You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run the following command to make sure you have the latest version of the pubsub emulator installed via gcloud:
10
+
```bash
11
+
gcloud components update pubsub-emulator
12
+
```
13
+
14
+
2. **Locate Emulator Directory**
15
+
The emulator represents a directory likely located at `<gcloud-install-path>/platform/pubsub-emulator`.
16
+
You can find the exact path by running the emulator and checking the output, or by inspecting where `gcloud` is installed (e.g. `which gcloud` usually points to a bin directory, and the platform directory is a sibling of `bin`).
17
+
Verify the version by running the emulator or checking the `VERSION` file if it exists.
18
+
19
+
3. **Package the Emulator**
20
+
Zip the directory found in the previous step. Name it `pubsub-emulator-<version>.zip`.
21
+
Ensure the zip structure is such that the top-level directory inside the zip is `pubsub-emulator`.
22
+
*Note: The existing code expects the binary at `pubsub-emulator-<version>/pubsub-emulator/bin/cloud-pubsub-emulator` inside the cache, which usually means the zip contains a root folder `pubsub-emulator`.*
23
+
24
+
4. **Upload to Storage**
25
+
Upload the zip file to the Firebase preview bucket:
"description": "Official Claude plugin for Firebase to help understand and manage your Firebase project, resources, and data",
9
+
"version": "1.0.0"
10
+
},
11
+
"plugins": [
12
+
{
13
+
"name": "firebase",
14
+
"description": "Claude plugin for Firebase that installs the Firebase MCP server and helps to manage Firebase projects, add backend services, add AI features, deploy & host apps, and more",
Copy file name to clipboardExpand all lines: .github/PULL_REQUEST_TEMPLATE.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ Run `npm test` to make sure your changes compile properly and the tests all pass
14
14
15
15
### Scenarios Tested
16
16
17
-
<!-- Write a list of all the user journeys and edge cases you've tested. Instructions for manual testing can be found at https://github.com/firebase/firebase-tools/blob/master/.github/CONTRIBUTING.md#development-setup -->
17
+
<!-- Write a list of all the user journeys and edge cases you've tested. Instructions for manual testing can be found at https://github.com/firebase/firebase-tools/blob/main/.github/CONTRIBUTING.md#development-setup -->
- run: "git diff --exit-code -- npm-shrinkwrap.json || (echo 'Error: npm-shrinkwrap.json is changed during npm install! Please make sure to use npm >= 8 and commit npm-shrinkwrap.json.' && false)"
@@ -300,15 +327,14 @@ jobs:
300
327
matrix:
301
328
node-version:
302
329
- "20"
303
-
- "22"
304
330
305
331
steps:
306
332
- uses: actions/checkout@v4
307
333
- name: Use Node.js ${{ matrix.node-version }}
308
334
uses: actions/setup-node@v3
309
335
with:
310
336
node-version: ${{ matrix.node-version }}
311
-
- run: npm i -g npm@9.5
337
+
- run: npm i -g npm@11.9
312
338
# --ignore-scripts prevents the `prepare` script from being run.
- run: "git diff --exit-code -- firebase-vscode/package-lock.json || (echo 'Error: firebase-vscode/package-lock.json is changed during npm install! Please make sure to use npm >= 8 and commit firebase-vscode/package-lock.json.' && false)"
0 commit comments