← FirebaseCONTENT HISTORY

Update to Firebase

Snapshot Nov 3, 2026 · 00:11 UTC · version 1.2.0

Collection source: downloaded plugin package. These snapshots do not have a confirmed matching collection source. Differences in file lists alone do not establish changes to the package.

WHAT CHANGED

Instructions updated for firebase-app-hosting-basics

Skill instructions — Now says: author: Google LLC ".next", ".vercel", 1. Create the backend if it does not exist (`apphosting:backends:list`; switch ...

Observed in instructions or declared skills. Runtime behavior has not been tested.

Save Firebase and check future changes in Following.

Up to 10 plugins free · no card required.

All fields and original values.

Skill instructions

Before

Sep 30, 2026 · 23:02 UTC

1. If the app needs safe access to sensitive keys, use `npx -y firebase-tools@latest apphosting:secrets` commands to set and grant access to secrets. deployments "git push" deployments. This is only recommended for more advanced ...

After

Nov 3, 2026 · 00:11 UTC

author: Google LLC ".next", ".vercel", 1. Create the backend if it does not exist (`apphosting:backends:list`; switch `--primary-region`, e.g. `us-east4`, if a region hits its 10-backend quota): ```bash npx -y ...

Supporting files

Before

Sep 30, 2026 · 23:02 UTC

[{"relative_path":"references/cli_commands.md","size_in_bytes":3217},{"relative_path":"references/configuration.md","size_in_bytes":1742},{"relative_path":"references/emulation.md","size_in_bytes":1493}]

After

Nov 3, 2026 · 00:11 UTC

[{"relative_path":"references/cli_commands.md","size_in_bytes":3217},{"relative_path":"references/configuration.md","size_in_bytes":1828},{"relative_path":"references/emulation.md","size_in_bytes":1493}]

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -3,6 +3,7 @@
 description: >-
   Deploys and manages full-stack web applications (Next.js, Angular) with Server-Side Rendering (SSR) using Firebase App Hosting. Use when deploying Next.js/Angular apps, configuring apphosting.yaml or firebase.json apphosting blocks, managing secrets, setting up GitHub CI/CD, or configuring Blaze billing requirements. Don't use for classic static web hosting, Auth, Firestore, Crashlytics, or Xcode.
 metadata:
+  author: Google LLC
   category: Serverless
 ---
 
@@ -39,7 +40,7 @@
 This is the recommended flow for most users.
 
 1. Configure `firebase.json` with an `apphosting` block.
-   
+
    ```json
    {
      "apphosting": {
@@ -48,6 +49,8 @@
        "ignore": [
          "node_modules",
          ".git",
+         ".next",
+         ".vercel",
          "firebase-debug.log",
          "firebase-debug.*.log",
          "functions"
@@ -55,21 +58,37 @@
      }
    }
    ```
+
 1. Create or edit `apphosting.yaml`- see
    [Configuration](references/configuration.md) for more information on how to
    do so.
-1. If the app needs safe access to sensitive keys, use
-   `npx -y firebase-tools@latest apphosting:secrets` commands to set and grant
-   access to secrets.
+
+1. Create the backend if it does not exist (`apphosting:backends:list`; switch
+   `--primary-region`, e.g. `us-east4`, if a region hits its 10-backend quota):
+
+   ```bash
+   npx -y firebase-tools@latest apphosting:backends:create --backend my-app-id --primary-region us-central1 --root-dir /
+   ```
+
+1. If the app needs safe access to sensitive keys, set and grant access after
+   creating the backend:
+
+   ```bash
+   printf '%s' '<value>' | npx -y firebase-tools@latest apphosting:secrets:set <secret-name> --data-file - --force
+   npx -y firebase-tools@latest apphosting:secrets:grantaccess <secret-name> --backend my-app-id
+   ```
+
 1. Run `npx -y firebase-tools@latest deploy` when you are ready to deploy.
 
 ### Automated deployment via GitHub (CI/CD)
 
 Alternatively, set up a backend connected to a GitHub repository for automated
-deployments "git push" deployments. This is only recommended for more advanced
-users, and is not required to use App Hosting. See
-[CLI Commands](references/cli_commands.md) for more information on how to set
-this up using CLI commands.
+"git push" deployments. For GitHub-connected backends, trigger rollouts with
+`npx -y firebase-tools@latest apphosting:rollouts:create <backend-id> --git-branch <branch>`
+(do not use `rollouts:create` when deploying from local source with `deploy`).
+
+For other backend or secret flags (`backends:get`, `backends:delete`, etc.), run
+`npx -y firebase-tools@latest <command> --help`.
 
 ## Emulation
 
Full technical diff · 2 changed fields

changed /included_files

BEFORE
[
  {
    "relative_path": "references/cli_commands.md",
    "size_in_bytes": 3217
  },
  {
    "relative_path": "references/configuration.md",
    "size_in_bytes": 1742
  },
  {
    "relative_path": "references/emulation.md",
    "size_in_bytes": 1493
  }
]
AFTER
[
  {
    "relative_path": "references/cli_commands.md",
    "size_in_bytes": 3217
  },
  {
    "relative_path": "references/configuration.md",
    "size_in_bytes": 1828
  },
  {
    "relative_path": "references/emulation.md",
    "size_in_bytes": 1493
  }
]

changed /skill_md_contents

BEFORE
"---\nname: firebase-app-hosting-basics\ndescription: >-\n  Deploys and manages full-stack web applications (Next.js, Angular) with Server-Side Rendering (SSR) using Firebase App Hosting. Use when deploying Next.js/Angular apps, configuring apphosting.yaml or firebase.json apphosting blocks, managing secrets, setting up GitHub CI/CD, or configuring Blaze billing requirements. Don't use for classic static web hosting, Auth, Firestore, Crashlytics, or Xcode.\nmetadata:\n  category: Serverless\n---\n\n# App Hosting Basics\n\n## Description\n\nThis skill enables the agent to deploy and manage modern, full-stack web\napplications (Next.js, Angular, etc.) using Firebase App Hosting.\n\n**Important**: In order to use App Hosting, your Firebase project must be on the\nBlaze pricing plan. Direct the user to\nhttps://console.firebase.google.com/project/_/overview?purchaseBillingPlan=metered\nto upgrade their plan.\n\n## Hosting vs App Hosting\n\n**Choose Firebase Hosting if:**\n\n- You are deploying a static site (HTML/CSS/JS).\n- You are deploying a simple SPA (React, Vue, etc. without SSR).\n- You want full control over the build and deploy process via CLI.\n\n**Choose Firebase App Hosting if:**\n\n- You are using a supported full-stack framework like Next.js or Angular.\n- You need Server-Side Rendering (SSR) or ISR.\n- You want an automated \"git push to deploy\" workflow with zero configuration.\n\n## Deploying to App Hosting\n\n### Deploy from Source\n\nThis is the recommended flow for most users.\n\n1. Configure `firebase.json` with an `apphosting` block.\n   \n   ```json\n   {\n     \"apphosting\": {\n       \"backendId\": \"my-app-id\",\n       \"rootDir\": \"/\",\n       \"ignore\": [\n         \"node_modules\",\n         \".git\",\n         \"firebase-debug.log\",\n         \"firebase-debug.*.log\",\n         \"functions\"\n       ]\n     }\n   }\n   ```\n1. Create or edit `apphosting.yaml`- see\n   [Configuration](references/configuration.md) for more information on how to\n   do so.\n1. If the app needs safe access to sensitive keys, use\n   `npx -y firebase-tools@latest apphosting:secrets` commands to set and grant\n   access to secrets.\n1. Run `npx -y firebase-tools@latest deploy` when you are ready to deploy.\n\n### Automated deployment via GitHub (CI/CD)\n\nAlternatively, set up a backend connected to a GitHub repository for automated\ndeployments \"git push\" deployments. This is only recommended for more advanced\nusers, and is not required to use App Hosting. See\n[CLI Commands](references/cli_commands.md) for more information on how to set\nthis up using CLI commands.\n\n## Emulation\n\nSee [Emulation](references/emulation.md) for more information on how to test\nyour app locally using the Firebase Local Emulator Suite.\n"
AFTER
"---\nname: firebase-app-hosting-basics\ndescription: >-\n  Deploys and manages full-stack web applications (Next.js, Angular) with Server-Side Rendering (SSR) using Firebase App Hosting. Use when deploying Next.js/Angular apps, configuring apphosting.yaml or firebase.json apphosting blocks, managing secrets, setting up GitHub CI/CD, or configuring Blaze billing requirements. Don't use for classic static web hosting, Auth, Firestore, Crashlytics, or Xcode.\nmetadata:\n  author: Google LLC\n  category: Serverless\n---\n\n# App Hosting Basics\n\n## Description\n\nThis skill enables the agent to deploy and manage modern, full-stack web\napplications (Next.js, Angular, etc.) using Firebase App Hosting.\n\n**Important**: In order to use App Hosting, your Firebase project must be on the\nBlaze pricing plan. Direct the user to\nhttps://console.firebase.google.com/project/_/overview?purchaseBillingPlan=metered\nto upgrade their plan.\n\n## Hosting vs App Hosting\n\n**Choose Firebase Hosting if:**\n\n- You are deploying a static site (HTML/CSS/JS).\n- You are deploying a simple SPA (React, Vue, etc. without SSR).\n- You want full control over the build and deploy process via CLI.\n\n**Choose Firebase App Hosting if:**\n\n- You are using a supported full-stack framework like Next.js or Angular.\n- You need Server-Side Rendering (SSR) or ISR.\n- You want an automated \"git push to deploy\" workflow with zero configuration.\n\n## Deploying to App Hosting\n\n### Deploy from Source\n\nThis is the recommended flow for most users.\n\n1. Configure `firebase.json` with an `apphosting` block.\n\n   ```json\n   {\n     \"apphosting\": {\n       \"backendId\": \"my-app-id\",\n       \"rootDir\": \"/\",\n       \"ignore\": [\n         \"node_modules\",\n         \".git\",\n         \".next\",\n         \".vercel\",\n         \"firebase-debug.log\",\n         \"firebase-debug.*.log\",\n         \"functions\"\n       ]\n     }\n   }\n   ```\n\n1. Create or edit `apphosting.yaml`- see\n   [Configuration](references/configuration.md) for more information on how to\n   do so.\n\n1. Create the backend if it does not exist (`apphosting:backends:list`; switch\n   `--primary-region`, e.g. `us-east4`, if a region hits its 10-backend quota):\n\n   ```bash\n   npx -y firebase-tools@latest apphosting:backends:create --backend my-app-id --primary-region us-central1 --root-dir /\n   ```\n\n1. If the app needs safe access to sensitive keys, set and grant access after\n   creating the backend:\n\n   ```bash\n   printf '%s' '<value>' | npx -y firebase-tools@latest apphosting:secrets:set <secret-name> --data-file - --force\n   npx -y firebase-tools@latest apphosting:secrets:grantaccess <secret-name> --backend my-app-id\n   ```\n\n1. Run `npx -y firebase-tools@latest deploy` when you are ready to deploy.\n\n### Automated deployment via GitHub (CI/CD)\n\nAlternatively, set up a backend connected to a GitHub repository for automated\n\"git push\" deployments. For GitHub-connected backends, trigger rollouts with\n`npx -y firebase-tools@latest apphosting:rollouts:create <backend-id> --git-branch <branch>`\n(do not use `rollouts:create` when deploying from local source with `deploy`).\n\nFor other backend or secret flags (`backends:get`, `backends:delete`, etc.), run\n`npx -y firebase-tools@latest <command> --help`.\n\n## Emulation\n\nSee [Emulation](references/emulation.md) for more information on how to test\nyour app locally using the Firebase Local Emulator Suite.\n"
Full snapshot data
{
  "description": "Deploys and manages full-stack web applications (Next.js, Angular) with Server-Side Rendering (SSR) using Firebase App Hosting. Use when deploying Next.js/Angular apps, configuring apphosting.yaml or firebase.json apphosting blocks, managing secrets, setting up GitHub CI/CD, or configuring Blaze billing requirements. Don't use for classic static web hosting, Auth, Firestore, Crashlytics, or Xcode.",
  "included_files": [
    {
      "relative_path": "references/cli_commands.md",
      "size_in_bytes": 3217
    },
    {
      "relative_path": "references/configuration.md",
      "size_in_bytes": 1828
    },
    {
      "relative_path": "references/emulation.md",
      "size_in_bytes": 1493
    }
  ],
  "name": "firebase-app-hosting-basics",
  "skill_md_contents": "---\nname: firebase-app-hosting-basics\ndescription: >-\n  Deploys and manages full-stack web applications (Next.js, Angular) with Server-Side Rendering (SSR) using Firebase App Hosting. Use when deploying Next.js/Angular apps, configuring apphosting.yaml or firebase.json apphosting blocks, managing secrets, setting up GitHub CI/CD, or configuring Blaze billing requirements. Don't use for classic static web hosting, Auth, Firestore, Crashlytics, or Xcode.\nmetadata:\n  author: Google LLC\n  category: Serverless\n---\n\n# App Hosting Basics\n\n## Description\n\nThis skill enables the agent to deploy and manage modern, full-stack web\napplications (Next.js, Angular, etc.) using Firebase App Hosting.\n\n**Important**: In order to use App Hosting, your Firebase project must be on the\nBlaze pricing plan. Direct the user to\nhttps://console.firebase.google.com/project/_/overview?purchaseBillingPlan=metered\nto upgrade their plan.\n\n## Hosting vs App Hosting\n\n**Choose Firebase Hosting if:**\n\n- You are deploying a static site (HTML/CSS/JS).\n- You are deploying a simple SPA (React, Vue, etc. without SSR).\n- You want full control over the build and deploy process via CLI.\n\n**Choose Firebase App Hosting if:**\n\n- You are using a supported full-stack framework like Next.js or Angular.\n- You need Server-Side Rendering (SSR) or ISR.\n- You want an automated \"git push to deploy\" workflow with zero configuration.\n\n## Deploying to App Hosting\n\n### Deploy from Source\n\nThis is the recommended flow for most users.\n\n1. Configure `firebase.json` with an `apphosting` block.\n\n   ```json\n   {\n     \"apphosting\": {\n       \"backendId\": \"my-app-id\",\n       \"rootDir\": \"/\",\n       \"ignore\": [\n         \"node_modules\",\n         \".git\",\n         \".next\",\n         \".vercel\",\n         \"firebase-debug.log\",\n         \"firebase-debug.*.log\",\n         \"functions\"\n       ]\n     }\n   }\n   ```\n\n1. Create or edit `apphosting.yaml`- see\n   [Configuration](references/configuration.md) for more information on how to\n   do so.\n\n1. Create the backend if it does not exist (`apphosting:backends:list`; switch\n   `--primary-region`, e.g. `us-east4`, if a region hits its 10-backend quota):\n\n   ```bash\n   npx -y firebase-tools@latest apphosting:backends:create --backend my-app-id --primary-region us-central1 --root-dir /\n   ```\n\n1. If the app needs safe access to sensitive keys, set and grant access after\n   creating the backend:\n\n   ```bash\n   printf '%s' '<value>' | npx -y firebase-tools@latest apphosting:secrets:set <secret-name> --data-file - --force\n   npx -y firebase-tools@latest apphosting:secrets:grantaccess <secret-name> --backend my-app-id\n   ```\n\n1. Run `npx -y firebase-tools@latest deploy` when you are ready to deploy.\n\n### Automated deployment via GitHub (CI/CD)\n\nAlternatively, set up a backend connected to a GitHub repository for automated\n\"git push\" deployments. For GitHub-connected backends, trigger rollouts with\n`npx -y firebase-tools@latest apphosting:rollouts:create <backend-id> --git-branch <branch>`\n(do not use `rollouts:create` when deploying from local source with `deploy`).\n\nFor other backend or secret flags (`backends:get`, `backends:delete`, etc.), run\n`npx -y firebase-tools@latest <command> --help`.\n\n## Emulation\n\nSee [Emulation](references/emulation.md) for more information on how to test\nyour app locally using the Firebase Local Emulator Suite.\n"
}

SHA-256 of public snapshot: 28f3738470047ccf660ca382d3eb24d51d9cceb0247e1be81d7900575f5da131