Update Firebase (major) #126
Open
Conversation
This file contains 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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
renovate
bot
force-pushed
the
renovate/major-firebase
branch
from
53b362b to
130a36e
Compare
renovate
bot
force-pushed
the
renovate/major-firebase
branch
from
130a36e to
054e336
Compare
renovate
bot
force-pushed
the
renovate/major-firebase
branch
from
054e336 to
756ae79
Compare
renovate
bot
force-pushed
the
renovate/major-firebase
branch
from
756ae79 to
c497298
Compare
renovate
bot
force-pushed
the
renovate/major-firebase
branch
from
c497298 to
1c03851
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR contains the following updates:
^2.0.12->^6.0.0^8.0.0->^9.0.0^11.4.0->^13.0.0^4.1.1->^6.0.06.3.018->22^6.3.3->^7.0.0Release Notes
open-cli-tools/concurrently (concurrently)
v9.1.2Compare Source
What's Changed
New Contributors
Full Changelog: open-cli-tools/concurrently@v9.1.1...v9.1.2
v9.1.1Compare Source
What's Changed
Full Changelog: open-cli-tools/concurrently@v9.1.0...v9.1.1
v9.1.0Compare Source
What's Changed
New Contributors
Full Changelog: open-cli-tools/concurrently@v9.0.1...v9.1.0
v9.0.1Compare Source
What's Changed
Full Changelog: open-cli-tools/concurrently@v9.0.0...v9.0.1
v9.0.0Compare Source
firebase/firebase-admin-node (firebase-admin)
v13.0.2: Firebase Admin Node.js SDK v13.0.2Compare Source
Bug Fixes
Miscellaneous
v13.0.1: Firebase Admin Node.js SDK v13.0.1Compare Source
Bug Fixes
Miscellaneous
v13.0.0: Firebase Admin Node.js SDK v13.0.0Compare Source
Breaking Changes
New Features
Bug Fixes
Miscellaneous
X-Goog-Api-Clientmetric header to outgoing authorized http requests (#2763)v12.7.0: Firebase Admin Node.js SDK v12.7.0Compare Source
New Features
Bug Fixes
@firebase/database-compattov1.0.8(#2739)Miscellaneous
X-Goog-Api-Clientmetric header to Auth and FCM requests (#2738)v12.6.0: Firebase Admin Node.js SDK v12.6.0Compare Source
New Features
Bug Fixes
Math.floor()when settingvalidDurationincreateSessionCookie()(#2712)Miscellaneous
v12.5.0: Firebase Admin Node.js SDK v12.5.0Compare Source
New Features
Bug Fixes
Miscellaneous
v12.4.0: Firebase Admin Node.js SDK v12.4.0Compare Source
Miscellaneous
v12.3.1: Firebase Admin Node.js SDK v12.3.1Compare Source
Bug Fixes
getToken()returns existing promise to a token if one exists instead of a new token. (#2648)Miscellaneous
v12.3.0: Firebase Admin Node.js SDK v12.3.0Compare Source
New Features
sendEach()andsendEachForMulticast()(#2550)Miscellaneous
v12.2.0: Firebase Admin Node.js SDK v12.2.0Compare Source
Breaking Changes
Bug Fixes
farmhashwithfarmhash-modern(#2603)Miscellaneous
v12.1.1: Firebase Admin Node.js SDK v12.1.1Compare Source
Bug Fixes
Miscellaneous
v12.1.0: Firebase Admin Node.js SDK v12.1.0Compare Source
New Features
Miscellaneous
set-outputdeprecation warnings (#2431)mailgun.jstov10.1.0(#2451)@actions/coreto ^1.10.1 to removeset-outputwarning and set action to use Node 20 (#2432)v12.0.0: Firebase Admin Node.js SDK v12.0.0Compare Source
Breaking change: Upgraded the
@google-cloud/firestore packageto v7. This is a breaking change. Refer to the Cloud Firestore release notes for more details.Breaking change: Upgraded the
@google-cloud/storage packageto v7. This is a breaking change. Refer to the Cloud Storage release notes for more details.Breaking change: Upgraded TypeScript to v5.1.6.
Deprecated support for Node.js 14. Instead use Node.js 16 or higher when deploying the Admin SDK. Node.js 14 support will be dropped in the next major version.
Upgraded the
google-cloud/firestoredependency to v7.1.0 to support sum() and `average() aggregation functions.Upgraded the
@firebase/database-compatpackage to v1.Dropped AutoML model support (#1974)
Bug Fixes
Miscellaneous
firebase/firebase-functions (firebase-functions)
v6.2.0Compare Source
v6.1.2Compare Source
v6.1.1Compare Source
v6.1.0Compare Source
v6.0.1Compare Source
v6.0.0Compare Source
v5.1.1Compare Source
enforceAppCheckoption for v2 onRequest trigger (#1477)v5.1.0Compare Source
v5.0.1Compare Source
v5.0.0Compare Source
v4.9.0Compare Source
v4.8.2Compare Source
Fix bug with CORS options for an array of one string (#1544)
v4.8.1Compare Source
Fix bug where 1st gen functions eventually fail with stack too deep (#1540)
Make simple CORS options static for improved debugability (#1536)
v4.8.0Compare Source
Add onInit callback function for global variable initialization (#1531)
v4.7.0Compare Source
nodejs/node (node)
v22.13.1Compare Source
v22.13.0Compare Source
v22.12.0Compare Source
v22.11.0Compare Source
v22.10.0: 2024-10-16, Version 22.10.0 (Current), @aduh95Compare Source
Notable Changes
New
"module-sync"exports conditionThis release introduces a
"module-sync"exports condition that's enabled whenrequire(esm)is enabled, so packages can supply a synchronous ES module to theNode.js module loader, no matter if it's being required or imported. This is
similar to the
"module"condition that bundlers have been using to supportrequire(esm)in Node.js, and allows dual-package authors to opt into ESM-firstonly on newer versions of Node.js that supports
require(esm)to avoid thedual-package hazard.
{ "type": "module", "exports": { "node": { // On new version of Node.js, both require() and import get // the ESM version "module-sync": "./index.js", // On older version of Node.js, where "module-sync" and require(esm) are // not supported, use the CJS version to avoid dual-package hazard. // When package authors think it's time to drop support for older versions of // Node.js, they can remove the exports conditions and just use "main": "index.js". "default": "./dist/index.cjs" }, // On any other environment, use the ESM version. "default": "./index.js" } }Or if the package is only meant to be run on Node.js and wants to fallback to
CJS on older versions that don't have
require(esm):{ "type": "module", "exports": { // On new version of Node.js, both require() and import get the ESM version "module-sync": "./index.js", // On older version of Node.js, where "module-sync" and require(esm) are // not supported, use the CJS version to avoid dual-package hazard. // When package authors think it's time to drop support for older versions of // Node.js, they can remove the exports conditions and just use "main": "index.js". "default": "./dist/index.cjs" } }For package authors: this only serves as a feature-detection mechanism for
packages that wish to support both CJS and ESM users during the period when some
active Node.js LTS versions support
require(esm)while some older ones don't.When all active Node.js LTS lines support
require(esm), packages can simplifytheir distributions by bumping the major version, dropping their CJS exports,
and removing the
module-syncexports condition (with onlymainordefaulttargetting the ESM exports). If the package needs to support both bundlers and
being run unbundled on Node.js during the transition period, use both
module-syncandmoduleand point them to the same ESM file. If the packagealready doesn't want to support older versions of Node.js that doesn't support
require(esm), don't use this export condition.For bundlers/tools: they should avoid implementing this stop-gap condition.
Most existing bundlers implement the de-facto bundler standard
moduleexports condition, and that should be enough to support users who want to bundle
ESM from CJS consumers. Users who want both bundlers and Node.js to recognize
the ESM exports can use both
module/module-syncconditions during thetransition period, and can drop
module-sync+modulewhen they no longer needto support older versions of Node.js. If tools do want to support this
condition, it's recommended to make the resolution rules in the graph pointed by
this condition match the Node.js native ESM rules to avoid divergence.
We ended up implementing a condition with a different name instead of reusing
"module", because existing code in the ecosystem using the"module"condition sometimes also expect the module resolution for these ESM files to
work in CJS style, which is supported by bundlers, but the native Node.js loader
has intentionally made ESM resolution different from CJS resolution (e.g.
forbidding
import './noext'orimport './directory'), so it would bebreaking to implement a
"module"condition without implementing the forbiddenESM resolution rules. For now, this just implements a new condition as
semver-minor so it can be backported to older LTS.
Contributed by Joyee Cheung in #54648.
node --runis now stableThis CLI flag runs a specified command from a
package.json'sConfiguration
📅 Schedule: Branch creation - "* 0-3 1 * *" (UTC), 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.
This PR was generated by Mend Renovate. View the repository job log.