Bump node-fetch and firebase in /js#340
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
Bumps [node-fetch](https://github.com/node-fetch/node-fetch) to 2.6.7 and updates ancestor dependency [firebase](https://github.com/firebase/firebase-js-sdk). These dependencies need to be updated together. Updates `node-fetch` from 2.6.1 to 2.6.7 - [Release notes](https://github.com/node-fetch/node-fetch/releases) - [Commits](node-fetch/node-fetch@v2.6.1...v2.6.7) Updates `firebase` from 7.24.0 to 9.22.0 - [Release notes](https://github.com/firebase/firebase-js-sdk/releases) - [Changelog](https://github.com/firebase/firebase-js-sdk/blob/master/CHANGELOG.md) - [Commits](https://github.com/firebase/firebase-js-sdk/compare/firebase@7.24.0...firebase@9.22.0) --- updated-dependencies: - dependency-name: node-fetch dependency-type: indirect - dependency-name: firebase dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
3 tasks
jpcottin
added a commit
that referenced
this pull request
May 15, 2026
Regenerate the lockfile inside a node:20 container so that every
transitive dep moves to the latest version that satisfies the existing
^x.y.z ranges in js/package.json. No top-level dep is bumped to a new
major.
Top-level package versions before / after:
- firebase 7.19.0 -> 7.24.0
- axios 1.4.0 -> 1.16.1
- @mui/material 5.13.1 -> 5.18.0
- @mui/icons-material 5.11.16 -> 5.18.0
- @mui/styles 5.13.1 -> 5.18.0
- @mui/lab 5.0.0-alpha.130 -> 5.0.0-alpha.177
- @emotion/react 11.11.0 -> 11.14.0
- @emotion/styled 11.11.0 -> 11.14.1
- react / react-dom / react-scripts / android-emulator-webrtc
unchanged
The 1400+ transitive bumps cover the security patches that were
proposed individually as #297, #304, #307, #310, #315, #321, #324,
#326, #340, #380, #381, and the more recent rollups #394, #395 (minus
their firebase 7 -> 12 jump, which would require a Firebase v9+
modular-API migration).
CI=true npm run build inside the same container produces a clean
production bundle (237.96 kB main.js gzipped).
Collaborator
|
Superseded by #398, which regenerates |
Contributor
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
Bot
deleted the
dependabot/npm_and_yarn/js/node-fetch-and-firebase-2.6.7
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps node-fetch to 2.6.7 and updates ancestor dependency firebase. These dependencies need to be updated together.
Updates
node-fetchfrom 2.6.1 to 2.6.7Release notes
Sourced from node-fetch's releases.
Commits
1ef4b56backport of #1449 (#1453)8fe5c4e2.x: Specify encoding as an optional peer dependency in package.json (#1310)f56b0c6fix(URL): prefer built in URL version when available and fallback to whatwg (...b5417aefix: import whatwg-url in a way compatible with ESM Node (#1303)18193c5fix v2.6.3 that did not sending query params (#1301)ace7536fix: properly encode url with unicode characters (#1291)152214cFix(package.json): Corrected main file path in package.json (#1274)Maintainer changes
This version was pushed to npm by endless, a new releaser for node-fetch since your current version.
Updates
firebasefrom 7.24.0 to 9.22.0Commits
60ff98dVersion Packages (#7290)6ee02eaMerge master into release9c6f972Try to log publish errors (#7295)6972de6Merge master into release6d332b4Update Node version to 16 in workflows (#7291)a0bb768Add label for GitHub Issue hotlist mirroring (#7287)2cdb529Merge master into release7bde55cDo docs check in one step (#7289)98d0b84Update README.md (#7286)e147219Remove the no-android tag from bloom filter spec tests, now that the feature ...Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.