Skip to content
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

Update Firebase (major) #126

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

Update Firebase (major) #126

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 1, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@types/supertest (source) ^2.0.12 -> ^6.0.0 age adoption passing confidence devDependencies major
concurrently ^8.0.0 -> ^9.0.0 age adoption passing confidence devDependencies major
firebase-admin (source) ^11.4.0 -> ^12.0.0 age adoption passing confidence dependencies major
firebase-functions ^4.1.1 -> ^6.0.0 age adoption passing confidence dependencies major
node (source) 18 -> 22 age adoption passing confidence engines major
supertest ^6.3.3 -> ^7.0.0 age adoption passing confidence devDependencies major

Release Notes

open-cli-tools/concurrently (concurrently)

v9.1.0

Compare Source

What's Changed

New Contributors

Full Changelog: open-cli-tools/concurrently@v9.0.1...v9.1.0

v9.0.1

Compare Source

What's Changed

Full Changelog: open-cli-tools/concurrently@v9.0.0...v9.0.1

v9.0.0

Compare Source

firebase/firebase-admin-node (firebase-admin)

v12.7.0: Firebase Admin Node.js SDK v12.7.0

Compare Source

New Features
  • feat(auth): Add recaptcha and sms toll fraud support for phone auth (#​2625)
Bug Fixes
  • fix: Pin @firebase/database-compat to v1.0.8 (#​2739)
Miscellaneous

v12.6.0: Firebase Admin Node.js SDK v12.6.0

Compare Source

New Features
Bug Fixes
  • fix(auth): Add missing Math.floor() when setting validDuration in createSessionCookie() (#​2712)
Miscellaneous

v12.5.0: Firebase Admin Node.js SDK v12.5.0

Compare Source

New Features
Bug Fixes
  • fix: updating comments with VibrateTimingsMillis and defaultVibrateTimings instead of vibrate_timings and default_vibrate_timings (#​2598)
  • fix: support httpAgent in JwksFetcher (#​2689)
Miscellaneous
  • [chore] Release 12.5.0 Take 2 (#​2703)
  • [chore] Release 12.5.0 (#​2702)
  • chore: Upgrade actions/upload-artifact@v4 (#​2700)
  • build(deps): bump actions/download-artifact in /.github/workflows (#​2694)
  • Create CHANGELOG.md (#​2626)

v12.4.0: Firebase Admin Node.js SDK v12.4.0

Compare Source

Miscellaneous

v12.3.1: Firebase Admin Node.js SDK v12.3.1

Compare Source

Bug Fixes
  • fix: 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.0

Compare Source

New Features
  • feat(fcm): Add HTTP2 support for sendEach() and sendEachForMulticast() (#​2550)
Miscellaneous

v12.2.0: Firebase Admin Node.js SDK v12.2.0

Compare Source

Breaking Changes
  • change: Deprecate Node.js 16 support (#​2574)
Bug Fixes
  • fix: Replace farmhash with farmhash-modern (#​2603)
  • fix: Make ADC + human account work with firebase-admin (#​2553)
  • fix: Use optional chaining in FirebaseError (#​2581)
Miscellaneous

v12.1.1: Firebase Admin Node.js SDK v12.1.1

Compare Source

Bug Fixes
Miscellaneous

v12.1.0: Firebase Admin Node.js SDK v12.1.0

Compare Source

New Features
  • feat(rc): Add server side Remote Config support (#​2529)
Miscellaneous

v12.0.0: Firebase Admin Node.js SDK v12.0.0

Compare Source

  • Breaking change: Upgraded the @google-cloud/firestore package to v7. This is a breaking change. Refer to the Cloud Firestore release notes for more details.

  • Breaking change: Upgraded the @google-cloud/storage package to 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/firestore dependency to v7.1.0 to support sum() and `average() aggregation functions.

  • Upgraded the @firebase/database-compat package to v1.

  • Dropped AutoML model support (#​1974)

Bug Fixes
  • fix(firestore): Export new aggregate types (#​2396)
Miscellaneous
firebase/firebase-functions (firebase-functions)

v6.1.0

Compare Source

  • Bump express version to 4.19.2 (#​1624)
  • Add support for beforeSmsSent auth blocking triggers. (#​1589)

v6.0.1

Compare Source

  • Fix bug where v1 functions can't be emulated (#​1615)

v6.0.0

Compare Source

  • Breaking: Change default entrypoint of the firebase-functions package to v2 instead of v1 (#​1594)
  • Add @​deprecated annotation on functions.config() API (#​1604)

v5.1.1

Compare Source

  • Fix retry in event triggered functions. (#​1463)
  • Expose retry configuration in v2 RTDB trigger (#​1588)
  • Fix CORS options for v2 callable functions (#​1564)
  • Remove invalid enforceAppCheck option for v2 onRequest trigger (#​1477)

v5.1.0

Compare Source

v5.0.1

Compare Source

  • Fix App fetching for named firestore instances (#​1562).

v5.0.0

Compare Source

  • Add option to get named firestore instance for v2 firestore functions (#​1550).
  • Remove firebase-admin v10 dependency for Firestore triggers multi-DB support (#​1555).

v4.9.0

Compare Source

  • Add new 2nd gen Firestore auth context triggers. (#​1519)

v4.8.2

Compare Source

Fix bug with CORS options for an array of one string (#​1544)

v4.8.1

Compare 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.0

Compare Source

Add onInit callback function for global variable initialization (#​1531)

v4.7.0

Compare Source

  • Fixes access on deeply nested, nonexistent property. (#​1432)
  • Add IteratedDataSnapshot interface to match with firebase admin v12 (#​1517).
  • Make bucket parameterizeable in storage functions (#​1518)
  • Introduce helper library for select and multi-select input (#​1518)
nodejs/node (node)

v22.11.0

Compare Source

v22.10.0: 2024-10-16, Version 22.10.0 (Current), @​aduh95

Compare Source

Notable Changes
New "module-sync" exports condition

This release introduces a "module-sync" exports condition that's enabled when
require(esm) is enabled, so packages can supply a synchronous ES module to the
Node.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 support
require(esm) in Node.js, and allows dual-package authors to opt into ESM-first
only on newer versions of Node.js that supports require(esm) to avoid the
dual-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 simplify
their distributions by bumping the major version, dropping their CJS exports,
and removing the module-sync exports condition (with only main or default
targetting 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-sync and module and point them to the same ESM file. If the package
already 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
module
exports 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-sync conditions during the
transition period, and can drop module-sync+module when they no longer need
to 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' or import './directory'), so it would be
breaking to implement a "module" condition without implementing the forbidden
ESM 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 --run is now stable

This CLI flag runs a specified command from a package.json's "scripts" object.

For the following package.json:

{
  "scripts": {
    "test": "node --test-reporter junit --test ./test"
  }
}

You can run node --run test and that would start the test suite.

Contributed by Yagiz Nizipli in #​53763.

Other notable changes
  • [f0b441230a] - (SEMVER-MINOR) crypto: add KeyObject.prototype.toCryptoKey (Filip Skokan) #​55262
  • [349d2ed07b] - (SEMVER-MINOR) crypto: add Date fields for validTo and validFrom (Andrew Moon) #​54159
  • [bebc95ed58] - doc: add abmusse to collaborators (Abdirahim Musse) #​55086
  • [914db60159] - (SEMVER-MINOR) http2: expose nghttp2_option_set_stream_reset_rate_limit as an option (Maël Nison) #​54875
  • [f7c3b03759] - (SEMVER-MINOR) lib: propagate aborted state to dependent signals before firing events (jazelly) #​54826
  • [32261fc98a] - (SEMVER-MINOR) module: support loading entrypoint as url (RedYetiDev) #​54933
  • [06957ff355] - (SEMVER-MINOR) module: implement flushCompileCache() (Joyee Cheung) #​54971
  • [2dcf70c347] - (SEMVER-MINOR) module: throw when invalid argument is passed to enableCompileCache() (Joyee Cheung) #​54971
  • [f9b19d7c44] - (SEMVER-MINOR) module: write compile cache to temporary file and then rename it (Joyee Cheung) #​54971
  • [e95163b170] - (SEMVER-MINOR) process: add process.features.require_module (Joyee Cheung) #​55241
  • [4050f68e5d] - (SEMVER-MINOR) process: add process.features.typescript (Aviv Keller) #​54295
  • [86f7cb802d] - (SEMVER-MINOR) test_runner: support custom arguments in run() (Aviv Keller) #​55126
  • [b62f2f8259] - (SEMVER-MINOR) test_runner: add 'test:summary' event (Colin Ihrig) #​54851
  • [d7c708aec5] - (SEMVER-MINOR) test_runner: add support for coverage via run() (Chemi Atlow) #​53937
  • [5fda4a1498] - (SEMVER-MINOR) worker: add markAsUncloneable api (Jason Zhang) #​55234
Commits

Configuration

📅 Schedule: Branch creation - "before 4am on the first day of the month" (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.


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

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

Copy link

vercel bot commented Jun 1, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
highlights ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 1, 2024 0:20am

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

Successfully merging this pull request may close these issues.

0 participants