Skip to content

build: update dependency firebase-tools to v14 #31

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Mar 29, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
firebase-tools ^13.0.0 -> ^14.0.0 age adoption passing confidence

Release Notes

firebase/firebase-tools (firebase-tools)

v14.0.1

Compare Source

  • Fixed a bug where the Admin SDK would not automatically connect to the Data Connect emulator when run in the Functions emulator. (#​8379)
  • Fix Cloud Functions deployment failure when service account is null. (#​8381)

v14.0.0

Compare Source

  • BREAKING(general)! Removed support for node 18.
  • BREAKING(apphosting)! init emulators App Hosting flow now creates apphosting.emulator.yaml with references to live secrets rather than apphosting.local.yaml with saved plaintext. apphosting:config:export command has been removed (#​8361)
  • BREAKING(apphosting)! Removed --location flag from apphosting commands. Instead, commands now prompt for primary region as needed.
  • BREAKING(dataconnect)! deploy dataconnect now warns about unsafe connector changes and insecure operations.
  • BREAKING(cloud functions)! Removed the experimental:functions:shell command. Use functions:shell instead.
  • Updated the Firebase Data Connect local toolkit to v2.0.0, which contains the following changes: (#​8370)
    • Added support for aggregate functions in queries.
    • BREAKING: New types for Generated React SDKs.
    • Improved description of various auto-generated mutation fields.
    • Fixed an issue where pnpm users' SDKs aren't linked properly.
  • apphosting:secrets:grantAccess can now grant access to emails and can grant multiple secrets at once (#​8357)
  • apphosting:secrets:set now has flows to help with test secrets (#​8359)
  • Updated init dataconnect templates to v1.
  • Fixed a bug where the emulator suite would set FIREBASE_DATACONNECT_EMULATOR_HOST instead of FIREBASE_DATA_CONNECT_EMULATOR_HOST.
  • Fixed a bug in Auth emulator where accounts:lookup is case-sensitive for emails (#​8344)
  • Fixed a bug where function deploys didn't support shorthand notation and parameterized service account (#​8366)
  • Fixed an issue where sql:setup would incorrectly remove the cloudsqlsuperuser role from firebasesuperuser (#​8363)
  • Fixed a bug where appdistribution:testers:list would error out if there were no testers.
  • Fixed a bug where Vertex AI API would not be automatically enabled when emulating Data Connect services that use it.

v13.35.1

Compare Source

  • Fix bug where functions:artifacts:setpolicy command's --none option didn't work as expected (#​8330)

v13.35.0

Compare Source

  • Added support for generated Angular SDKs for Data Connect
  • App Hosting emulator can now load secret env vars. (#​8305)
  • Fixed webframeworks deployments when using multiple hosting sites in firebase.json. (#​8314)
  • Added a new command to setup a cleanup policy for functions artifacts. (#​8268)
  • Added support for 3rd party builders for Angular. (#​7557)
  • Fixed GCF V2 artifact cleanup by correctly encoding artifact names to match GCF V2's format. (#​8318)
  • Increase emulator UI body parser limit to match Storage emulator maximum. (#​8329)
  • Fixed Data Connect setup issues for fresh databases due to IAM user not being created. (#​8335)
  • Fixed an issue where ext:install used POSIX file seperators on Windows machines. (#​8326)
  • Updated the Firebase Data Connect local toolkit to v1.9.2, which adds support for generated Angular SDKs and updates Dart SDK fields to follow best practices. (#​8347)
  • Fixed an issue where credentials from firebase login would not be correctly provided to the Data Connect emulator.
  • Fixed misleading comments in firebase init dataconnect connector.yaml template.
  • Improved Data Connect SQL permissions to better handle tables owned by IAM roles. (#​8339)
  • Fixed an issue where the Data Connect emulator would crash after some SQL errors.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

See associated pull request for more information.
Copy link
Author

renovate bot commented Mar 29, 2025

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: undefined
Post-upgrade command 'git restore .yarn/releases/yarn-1.22.22.cjs' has not been added to the allowed list in allowedCommands
File name: undefined
Post-upgrade command 'yarn install --frozen-lockfile --non-interactive' has not been added to the allowed list in allowedCommands
File name: undefined
Post-upgrade command 'yarn ng-dev misc update-generated-files' has not been added to the allowed list in allowedCommands

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants