Version Packages

[google-oss-bot]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to release, this PR will be updated.

Releases

@firebase/[email protected]

Major Changes

• 980c7d539 #3378 - Release @firebase/rules-unit-testing to replace the @firebase/testing package. The new
  package is API compatible but has the following breaking behavior changes:

  • assertFails() will now only fail on PERMISSION DENIED errors, not any error.
  • initializeAdminApp() now relies on firebase-admin rather than imitating the Admin SDK.

Patch Changes

• Updated dependencies [67501b980]:
  • [email protected]

[email protected]

Minor Changes

• 67501b980 #3424 - Issue 2393 - Add environment check to Performance Module

Patch Changes

• Updated dependencies [67501b980, 960093d5b, b97c7e758]:
  • @firebase/[email protected]
  • @firebase/[email protected]

@firebase/[email protected]

Minor Changes

• 67501b980 #3424 - Issue 2393 - Add environment check to Performance Module

@firebase/[email protected]

Patch Changes

• 960093d5b #3575 (fixes #2755) - terminate() can now be retried if it fails with an IndexedDB exception.

• b97c7e758 #3487 - Enable fallback for auto-generated identifiers in environments that support crypto but not crypto.getRandomValues.

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[google-oss-bot]

Binary Size Report

Affected SDKs

• @firebase/performance

  Type	Base (67501b9)	Head (5eca71f)	Diff
  browser	27.4 kB	27.4 kB	-1 B (-0.0%)
  esm2017	25.4 kB	25.4 kB	-1 B (-0.0%)
  main	27.4 kB	27.4 kB	-1 B (-0.0%)
  module	27.1 kB	27.1 kB	-1 B (-0.0%)

• firebase

  Type	Base (67501b9)	Head (5eca71f)	Diff
  firebase-performance-standalone.es2017.js	71.3 kB	71.3 kB	-3 B (-0.0%)
  firebase-performance-standalone.js	47.9 kB	47.9 kB	-2 B (-0.0%)
  firebase-performance.js	38.3 kB	38.3 kB	-2 B (-0.0%)
  firebase.js	823 kB	823 kB	-2 B (-0.0%)

Test Logs

• Base (67501b98): https://github.com/firebase/firebase-js-sdk/actions/runs/214248597
• Head (5eca71f5): https://github.com/firebase/firebase-js-sdk/actions/runs/214251772