Skip to content

build: update all non-major dependencies #31406

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

Merged

Conversation

angular-robot
Copy link
Collaborator

This PR contains the following updates:

Package Type Update Change
@bazel/buildifier devDependencies patch 8.2.0 -> 8.2.1
@types/node (source) devDependencies patch 22.15.21 -> 22.15.32
firebase-tools devDependencies minor 14.4.0 -> 14.8.0
jasmine (source) devDependencies minor 5.7.1 -> 5.8.0
jasmine-core (source) devDependencies minor 5.7.1 -> 5.8.0
jasmine-core (source) devDependencies minor ~5.7.0 -> ~5.8.0
sass devDependencies patch 1.89.0 -> 1.89.2

Release Notes

bazelbuild/buildtools (@​bazel/buildifier)

v8.2.1: Release 8.2.1 (2025-06-10)

Compare Source

What's Changed

New Contributors

Full Changelog: bazelbuild/buildtools@v8.2.0...v8.2.1

firebase/firebase-tools (firebase-tools)

v14.8.0

Compare Source

  • Updated the Data Connect emulator to use pglite 0.3.x and Postgres 17, which fixes some crashes related to wire protocol inconsistencies. (#​8679, #​8658)
  • Remove container cleanup logic in functions:delete command (#​8771)
  • Fixed an issue where the IAM enablement for GenKit monitoring would try to change an invalid service account. (#​8756)
  • Added a max instance default to function templates and comments educating users on cost controls. (#​8772)
  • Added caching to API enablement checks to reduce burn of serviceusage.googleapis.com quota.
  • Updated the Firebase Data Connect local toolkit to v2.7.1, which includes the following changes
    • Kotlin codegen: Add a default value for the block_ parameter to execute() so that it is not necessary to specify empty {} for operations with optional variables and none are specified.
    • Web SDK READMEs will link to other web framework READMEs for better discoverability.

v14.7.0

Compare Source

  • Add emulator support to firebase storage MCP tools. (#​8707)
  • Removed overeager error catch in functions:list.
  • Add validation during firebase init feature selection. (#​5232)
  • Fixed an issue where the extensions emulator did not work with demo- projects. (#​8720)
  • Fixed issue where --export-on-exit fails if the target directory does not exist. (#​4688)
  • Fixed issue where the Firebase MCP server could not use application default credentials. (#​8671)
  • Updated the Firebase Data Connect local toolkit to v2.7.0, which includes the following changes: (#​8743)
    • Fixed an issue where unwanted link dependencies are added to package.json when multiple package managers are used in a web project.
    • Added linter warnings for naming convention violations & missing join table @table(key).

v14.6.0

Compare Source

  • Fixed issue where projects:create didn't correctly parse the projectId and displayName input. (#​8634)
  • Improved GetDatabase API call caching for Firestore function deployments. (#​8681)
  • Increased timeout for linking CloudSQL instances to Data Connect.
  • Fixed issue where firebase use --add didn't correctly set the active project. (#​8694)
  • Correctly support '--database' flag in firestore:delete. (#​6753)
  • Always setup Data Connect SDK when FDC_CONNECTOR env var is set.
  • firebase init now uses FIREBASE_PROJECT env var as the default project name.
  • Add emulator support to firestore MCP tools. (#​8700)
  • Increased npm timeout for web frameworks to 60s. (#​8702)
  • Fallback to reading web framework dependencies version directly from node_modules package.json when the npm timeout is reached. (#​8702)
  • Updated the Firebase Data Connect local toolkit to v2.6.3, which includes some cleanups and error message improvements. (#​8667)

v14.5.1

Compare Source

  • Fixed an issue where 'firestore.database' was accidentally treated as a required field. (#​8678)

v14.5.0

Compare Source

  • WARNING - This version accidentally included a breaking change where firestore.database was treated as a required field in firebase.json. This is addressed in 14.5.1.
  • Improve log messages on skipped App Hosting source deploys. (#​8674)
  • Fixed issue in init where users were forced to specify emulator UI port (#​8626)
  • Added MCP tools for App Hosting (#​8605)
  • Fixed crash when starting the App Hosting emulator in certain applications (#​8624)
  • Fixed issue where, with webframeworks enabled, firebase init hosting re-prompts users for source. (#​8587)
  • Updated typescript version in functions template to avoid build issue with @​google-cloud/storage depedency (#​8194)
  • Updated the Firebase Data Connect local toolkit to v2.6.2, which includes the following changes: (#​8667)
    • Improved error messages of auth.uid in CEL expressions when unauthenticated.
    • Fixed a bug where ExecuteGraphql with vector embedding in emulator fails due to missing context.
  • Improved firebase init firestore + firebase deploy flow on a fresh new project without going to Console (#​8653)
  • Added support for Angular v20 to Firebase Hosting (#​8672)
jasmine/jasmine-npm (jasmine)

v5.8.0

Compare Source

Please see the release notes.

jasmine/jasmine (jasmine-core)

v5.8.0

Compare Source

Please see the release notes.

sass/dart-sass (sass)

v1.89.2

Compare Source

Embedded Host
  • Fixed a compilation error caused by an outdated buf dependency.

v1.89.1

Compare Source

  • No user-visible changes.

Configuration

📅 Schedule: Branch creation - "after 10:00pm every weekday,before 5:00am every weekday,every weekend" in timezone America/Tijuana, 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

This PR has been generated by Renovate Bot.

@angular-robot angular-robot requested a review from a team as a code owner June 24, 2025 08:41
@angular-robot angular-robot added action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project labels Jun 24, 2025
@angular-robot angular-robot requested review from crisbeto and andrewseguin and removed request for a team June 24, 2025 08:41
@angular-robot angular-robot added action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project labels Jun 24, 2025
See associated pull request for more information.
@angular-robot angular-robot force-pushed the ng-renovate/all-non-major-dependencies branch from d6f7337 to 812171d Compare June 24, 2025 09:38
@angular-robot
Copy link
Collaborator Author

⚠️ Artifact update problem

Renovate failed to update an artifact 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: docs/src/assets/stackblitz/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: example-app@0.0.0
npm error Found: karma-jasmine@4.0.2
npm error node_modules/karma-jasmine
npm error   dev karma-jasmine@"~4.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer karma-jasmine@"^5.0.0" from karma-jasmine-html-reporter@2.1.0
npm error node_modules/karma-jasmine-html-reporter
npm error   dev karma-jasmine-html-reporter@"~2.1.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2025-06-24T09_37_51_894Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-06-24T09_37_51_894Z-debug-0.log

@crisbeto crisbeto added the target: patch This PR is targeted for the next patch release label Jun 24, 2025
@crisbeto crisbeto added target: minor This PR is targeted for the next minor release and removed target: patch This PR is targeted for the next patch release labels Jun 24, 2025
@crisbeto crisbeto removed the request for review from andrewseguin June 24, 2025 11:12
@crisbeto crisbeto merged commit d07af6e into angular:main Jun 24, 2025
26 of 28 checks passed
@angular-robot angular-robot deleted the ng-renovate/all-non-major-dependencies branch June 24, 2025 11:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project target: minor This PR is targeted for the next minor release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants