firebase
diff --git a/‎.agent/skills/resolve-docker-vulnerabilities/SKILL.md‎
Lines changed: 58 additions & 0 deletions b/‎.agent/skills/resolve-docker-vulnerabilities/SKILL.md‎
Lines changed: 58 additions & 0 deletions
diff --git a/‎.github/workflows/node-test.yml‎
Lines changed: 11 additions & 3 deletions b/‎.github/workflows/node-test.yml‎
Lines changed: 11 additions & 3 deletions
diff --git a/‎.gitignore‎
Lines changed: 1 addition & 0 deletions b/‎.gitignore‎
Lines changed: 1 addition & 0 deletions
diff --git a/‎.mocharc.yml‎
Lines changed: 1 addition & 1 deletion b/‎.mocharc.yml‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎firebase-vscode/CHANGELOG.md‎
Lines changed: 4 additions & 0 deletions b/‎firebase-vscode/CHANGELOG.md‎
Lines changed: 4 additions & 0 deletions
diff --git a/‎firebase-vscode/README.md‎
Lines changed: 6 additions & 6 deletions b/‎firebase-vscode/README.md‎
Lines changed: 6 additions & 6 deletions
diff --git a/‎firebase-vscode/package-lock.json‎
Lines changed: 2 additions & 2 deletions b/‎firebase-vscode/package-lock.json‎
Lines changed: 2 additions & 2 deletions
diff --git a/‎firebase-vscode/package.json‎
Lines changed: 8 additions & 8 deletions b/‎firebase-vscode/package.json‎
Lines changed: 8 additions & 8 deletions
diff --git a/‎firebase-vscode/package.nls.json‎
Lines changed: 1 addition & 1 deletion b/‎firebase-vscode/package.nls.json‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎firebase-vscode/src/analytics.ts‎
Lines changed: 1 addition & 1 deletion b/‎firebase-vscode/src/analytics.ts‎
Lines changed: 1 addition & 1 deletion
@@ -0,0 +1,58 @@
+---
+name: resolve-docker-vulnerabilities
+description: Skill to resolve Docker vulnerabilities for the firebase-cli image. Use this skill when you need to check for vulnerabilities in the firebase-cli Docker image and address them.
+---
+
+# Resolve Docker Vulnerabilities
+
+This skill guides you through the process of listing images, checking for vulnerabilities, planning remediation, and verifying the fixes by publishing to a staging repository.
+
+## Workflow
+
+### 1. Publish to Staging
+
+Run the build on `fir-tools-builds` and publish to the `staging` repository in `firebase-cli` to see the baseline vulnerabilities after the build's own updates.
+
+```bash
+./scripts/publish/firebase-docker-image/run.sh --build-project fir-tools-builds --repo staging --target firebase-cli
+```
+
+### 2. Check Vulnerabilities
+
+Check the vulnerability reports for the image just pushed to staging. You will need to find the digest of the image first.
+
+```bash
+gcloud artifacts docker images list us-docker.pkg.dev/firebase-cli/staging/firebase
+```
+
+Then check vulnerabilities using the digest:
+
+```bash
+gcloud artifacts vulnerabilities list us-docker.pkg.dev/firebase-cli/staging/firebase@sha256:<DIGEST>
+```
+
+To investigate which layers and file paths are causing the vulnerabilities, run the command with `--format=json`:
+
+```bash
+gcloud artifacts vulnerabilities list us-docker.pkg.dev/firebase-cli/staging/firebase@sha256:<DIGEST> --format=json
+```
+
+Look for `fileLocation` and `layerDetails` in the output to understand if the vulnerability is in:
+- Project dependencies (e.g., under `/usr/local/node_packages/node_modules`). Recommend updating the package.json and running the build again. You can use overrides as needed here to upgrade transitive dependencies to non-breaking versions.
+- Global tools (e.g., under `/usr/local/lib/node_modules/npm`). Recommend waiting for upstream fixes (which will be pulled in as soon as they are available).
+- External binaries (e.g., emulator JARs under `/root/.cache/firebase/emulators`). Recommend raising these issues to the team owning the emulator.
+
+### 3. Plan Remediation
+
+For each vulnerable package identified:
+- Determine if it can be updated in the Dockerfile.
+- Check if a fix is available.
+- Create a plan to address it (e.g., upgrading the base image, upgrading the specific package).
+
+### 4. Present Plan to User
+
+Present the proposed plan to the user for approval before making changes.
+
+### 5. Apply Fix and Re-Verify
+
+After making changes to the Dockerfile or related files, repeat Step 1 and Step 2 to publish a new staged image and verify that the vulnerabilities have been resolved.
@@ -65,7 +65,7 @@ jobs:
         working-directory: firebase-vscode
       - run: npm run test:unit
         working-directory: firebase-vscode
-      - uses: codecov/codecov-action@v3
+      - uses: codecov/codecov-action@v5
         if: matrix.node-version == '20'
 
   # vscode_integration:
@@ -123,7 +123,7 @@ jobs:
   #         name: screenshots
   #         path: firebase-vscode/src/test/screenshots
 
-  #     - uses: codecov/codecov-action@v3
+  #     - uses: codecov/codecov-action@v5
   #       if: matrix.node-version == '20'
 
   agent_evals_build:
@@ -163,11 +163,19 @@ jobs:
           cache: npm
           cache-dependency-path: npm-shrinkwrap.json
 
+      - name: Cache ESLint
+        uses: actions/cache@v4
+        with:
+          path: .eslintcache
+          key: eslint-${{ runner.os }}-node${{ matrix.node-version }}-${{ hashFiles('**/*.ts', '**/*.js') }}
+          restore-keys: |
+            eslint-${{ runner.os }}-node${{ matrix.node-version }}-
+
       - run: npm i -g npm@9.5
       - run: npm ci
       - run: npm test -- -- --forbid-only
 
-      - uses: codecov/codecov-action@v3
+      - uses: codecov/codecov-action@v5
         if: matrix.node-version == '20'
 
   integration:
 
@@ -20,6 +20,7 @@ test_output.log
 scripts/emulator-tests/functions/index.js
 yarn.lock
 .npmrc
+.eslintcache
 *.tsbuildinfo
 
 .DS_Store
 
@@ -4,7 +4,7 @@ require:
   - src/test/helpers/mocha-bootstrap.ts
 file:
   - src/test/helpers/global-mock-auth.ts
-timeout: 1000
+timeout: 2000
 recursive: true
 node-options:
   - no-experimental-strip-types
@@ -1,5 +1,9 @@
 ## NEXT
 
+## 2.3.0
+
+- Rename product from Firebase Data Connect to Firebase SQL Connect.
+
 ## 2.2.3
 
 - Update internal `firebase-tools` dependency to 15.13.0
 
@@ -1,12 +1,12 @@
-# Firebase Data Connect for VSCode
+# Firebase SQL Connect for VSCode
 
-The Firebase Data Connect extension provides a suite of tools to assist developers in their Data Connect development workflow.
+The Firebase SQL Connect extension provides a suite of tools to assist developers in their SQL Connect development workflow.
 
 ![Extension Demo Gif](https://www.gstatic.com/mobilesdk/241004_mobilesdk/fdc_extension_readme.gif)
 
 ## Language Features
 
-The extension runs a Graphql Language Server that checks for syntax and compile time errors in your Data Connect code. Additionally, it provides auto-complete suggestions specific to Data Connect.
+The extension runs a Graphql Language Server that checks for syntax and compile time errors in your SQL Connect code. Additionally, it provides auto-complete suggestions specific to SQL Connect.
 
 The extension will automatically generate GraphQL types based on your schema, viewable in your Explorer panel.
 
@@ -16,9 +16,9 @@ Within your GraphQL files, you’ll see in-line Codelenses that can help you cre
 
 In your schema files, click on `Add Data` or `Read Data` to generate a corresponding operation to populate or read from your DB.
 
-To execute an operation, click on `Run Local` or `Run Production`. This will execute your operation against the emulators, or your production Data Connect instance.
+To execute an operation, click on `Run Local` or `Run Production`. This will execute your operation against the emulators, or your production SQL Connect instance.
 
-Note: You’ll need to start the Data Connect emulator in order to execute operations locally.
+Note: You’ll need to start the SQL Connect emulator in order to execute operations locally.
 
 ## Strongly typed SDK Generation
 
@@ -34,4 +34,4 @@ Once you’ve tested the schema and operations and ran the generated SDK in your
 
 ### Documentation
 
-Please see [Getting started with Firebase Data Connect](https://firebase.google.com/docs/data-connect/quickstart).
+Please see [Getting started with Firebase SQL Connect](https://firebase.google.com/docs/data-connect/quickstart).
@@ -1,10 +1,10 @@
 {
   "name": "firebase-dataconnect-vscode",
-  "displayName": "Firebase Data Connect",
+  "displayName": "Firebase SQL Connect",
   "publisher": "GoogleCloudTools",
   "icon": "./resources/firebase_dataconnect_logo.png",
-  "description": "Firebase Data Connect for VSCode",
-  "version": "2.2.3",
+  "description": "Firebase SQL Connect for VSCode",
+  "version": "2.3.0",
   "engines": {
     "vscode": "^1.69.0"
   },
@@ -36,7 +36,7 @@
       },
       {
         "command": "fdc.deploy",
-        "title": "Firebase Data Connect: Deploy",
+        "title": "Firebase SQL Connect: Deploy",
         "icon": "$(cloud-upload)"
       },
       {
@@ -45,7 +45,7 @@
       },
       {
         "command": "firebase.refresh",
-        "title": "Firebase Data Connect Extension: Refresh"
+        "title": "Firebase SQL Connect Extension: Refresh"
       }
     ],
     "configuration": {
@@ -111,14 +111,14 @@
       "activitybar": [
         {
           "id": "firebase-data-connect",
-          "title": "Firebase Data Connect",
+          "title": "Firebase SQL Connect",
           "icon": "resources/firebase_dataconnect_logo.svg"
         }
       ],
       "panel": [
         {
           "id": "firebase-data-connect-execution-view",
-          "title": "Data Connect Execution",
+          "title": "SQL Connect Execution",
           "icon": "$(gmp-data-connect)"
         }
       ]
@@ -132,7 +132,7 @@
         }
       },
       "gmp-data-connect": {
-        "description": "Data Connect icon",
+        "description": "SQL Connect icon",
         "default": {
           "fontPath": "./resources/GMPIcons.woff2",
           "fontCharacter": "\\gmp_nav20_dataconnect"
 
@@ -4,7 +4,7 @@
   "ext.config.firebasePath": "Path to the `Firebase` module, e.g. `./node_modules/firebase`",
   "ext.config.hosting.useFrameworks": "Enable web frameworks",
   "ext.config.npmPath": "Path to NPM executable in local environment",
-  "ext.config.title": "Firebase Data Connect",
+  "ext.config.title": "Firebase SQL Connect",
   "ext.config.idx.viewMetricNotice": "Show data collection notice on next startup (IDX Only)",
   "ext.config.emulators.importPath": "Path to import emulator data from",
   "ext.config.emulators.exportPath": "Path to export emulator data to",
 
@@ -5,7 +5,7 @@ import { env as monospaceEnv } from "../src/core/env";
 import { getSettings } from "./utils/settings";
 
 export const IDX_METRIC_NOTICE = `
-When you use the Firebase Data Connect Extension, Google collects telemetry data such as usage statistics, error metrics, and crash reports. Telemetry helps us better understand how the Firebase Extension is performing, where improvements need to be made, and how features are being used. Firebase uses this data, consistent with our [Google Privacy Policy](https://policies.google.com/privacy?hl=en-US), to provide, improve, and develop Firebase products and services.
+When you use the Firebase SQL Connect Extension, Google collects telemetry data such as usage statistics, error metrics, and crash reports. Telemetry helps us better understand how the Firebase Extension is performing, where improvements need to be made, and how features are being used. Firebase uses this data, consistent with our [Google Privacy Policy](https://policies.google.com/privacy?hl=en-US), to provide, improve, and develop Firebase products and services.
 We take steps to protect your privacy as part of this process. This includes disconnecting your telemetry data from your Google Account, fully anonymizing it, and storing that data for up to 14 months.
 Read more in our [Privacy Policy](https://policies.google.com/privacy?hl=en-US).
 `;
Original file line number	Diff line number	Diff line change
`@@ -1,10 +1,10 @@`
`1`	`1`	`{`
`2`	`2`	`"name": "firebase-dataconnect-vscode",`
`3`		`- "displayName": "Firebase Data Connect",`
	`3`	`+ "displayName": "Firebase SQL Connect",`
`4`	`4`	`"publisher": "GoogleCloudTools",`
`5`	`5`	`"icon": "./resources/firebase_dataconnect_logo.png",`
`6`		`- "description": "Firebase Data Connect for VSCode",`
`7`		`- "version": "2.2.3",`
	`6`	`+ "description": "Firebase SQL Connect for VSCode",`
	`7`	`+ "version": "2.3.0",`
`8`	`8`	`"engines": {`
`9`	`9`	`"vscode": "^1.69.0"`
`10`	`10`	`},`
`@@ -36,7 +36,7 @@`
`36`	`36`	`},`
`37`	`37`	`{`
`38`	`38`	`"command": "fdc.deploy",`
`39`		`- "title": "Firebase Data Connect: Deploy",`
	`39`	`+ "title": "Firebase SQL Connect: Deploy",`
`40`	`40`	`"icon": "$(cloud-upload)"`
`41`	`41`	`},`
`42`	`42`	`{`
`@@ -45,7 +45,7 @@`
`45`	`45`	`},`
`46`	`46`	`{`
`47`	`47`	`"command": "firebase.refresh",`
`48`		`- "title": "Firebase Data Connect Extension: Refresh"`
	`48`	`+ "title": "Firebase SQL Connect Extension: Refresh"`
`49`	`49`	`}`
`50`	`50`	`],`
`51`	`51`	`"configuration": {`
`@@ -111,14 +111,14 @@`
`111`	`111`	`"activitybar": [`
`112`	`112`	`{`
`113`	`113`	`"id": "firebase-data-connect",`
`114`		`- "title": "Firebase Data Connect",`
	`114`	`+ "title": "Firebase SQL Connect",`
`115`	`115`	`"icon": "resources/firebase_dataconnect_logo.svg"`
`116`	`116`	`}`
`117`	`117`	`],`
`118`	`118`	`"panel": [`
`119`	`119`	`{`
`120`	`120`	`"id": "firebase-data-connect-execution-view",`
`121`		`- "title": "Data Connect Execution",`
	`121`	`+ "title": "SQL Connect Execution",`
`122`	`122`	`"icon": "$(gmp-data-connect)"`
`123`	`123`	`}`
`124`	`124`	`]`
`@@ -132,7 +132,7 @@`
`132`	`132`	`}`
`133`	`133`	`},`
`134`	`134`	`"gmp-data-connect": {`
`135`		`- "description": "Data Connect icon",`
	`135`	`+ "description": "SQL Connect icon",`
`136`	`136`	`"default": {`
`137`	`137`	`"fontPath": "./resources/GMPIcons.woff2",`
`138`	`138`	`"fontCharacter": "\\gmp_nav20_dataconnect"`