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/auth@0.18.0

Minor Changes

• 4d2a54fb0 #5527 - Update all persistences to map to inMemoryPersistence in Node, to avoid errors with server-side rendering

Patch Changes

• a5d87bc5c #5511 - Fix bug with the user emailVerified field persistence across tabs

• 07b88e6e8 #5487 - Add missing phone FACTOR_ID static property to the PhoneMultiFactorGenerator class

• c2362214a #5522 - Fix wrongly-typed tenantId fields in requests to some endpoints

• Updated dependencies [a99943fe3, b835b4cba]:

  • @firebase/logger@0.3.0
  • @firebase/util@1.4.0
  • @firebase/component@0.5.7

firebase@9.1.0

Minor Changes

• f90c1d081 #3623 - Issue 2393 - Add environment check to Remote-Config Module

Patch Changes

• Updated dependencies [dfe65ff9b, b835b4cba, f90c1d081, 08c098211, f78ceca1c, e62d02e52, a5d87bc5c, a99943fe3, b835b4cba, 07b88e6e8, b835b4cba, b835b4cba, 4d2a54fb0, c2362214a, b79bd33e4, a99943fe3]:
  • @firebase/database-compat@0.1.1
  • @firebase/database@0.12.1
  • @firebase/app-check@0.4.1
  • @firebase/app-check-compat@0.1.2
  • @firebase/remote-config@0.3.0
  • @firebase/firestore-compat@0.1.3
  • @firebase/firestore@3.1.0
  • @firebase/auth@0.18.0
  • @firebase/util@1.4.0
  • @firebase/performance@0.5.1
  • @firebase/performance-compat@0.1.1
  • @firebase/messaging@0.9.1
  • @firebase/analytics@0.7.1
  • @firebase/messaging-compat@0.1.1
  • @firebase/analytics-compat@0.1.2
  • @firebase/remote-config-compat@0.1.1
  • @firebase/auth-compat@0.1.3
  • @firebase/storage@0.8.3
  • @firebase/app@0.7.1
  • @firebase/app-compat@0.1.2
  • @firebase/functions@0.7.2
  • @firebase/functions-compat@0.1.3
  • @firebase/installations@0.5.1
  • @firebase/storage-compat@0.1.3

@firebase/firestore@3.1.0

Minor Changes

• f78ceca1c #5394 - Fixed a bug where UpdateData did not recognize union types or optional, dot-separated string fields.

Patch Changes

• a99943fe3 #5539 - use constructor.name for Object type

• Updated dependencies [a99943fe3, 456d664ae, b835b4cba]:

  • @firebase/logger@0.3.0
  • @firebase/util@1.4.0
  • @firebase/webchannel-wrapper@0.6.0
  • @firebase/component@0.5.7

@firebase/logger@0.3.0

Minor Changes

• a99943fe3 #5539 - Use esm2017 builds by default

@firebase/remote-config@0.3.0

Minor Changes

• f90c1d081 #3623 - Issue 2393 - Add environment check to Remote-Config Module

Patch Changes

• Updated dependencies [a99943fe3, b835b4cba]:
  • @firebase/logger@0.3.0
  • @firebase/util@1.4.0
  • @firebase/component@0.5.7
  • @firebase/installations@0.5.1

@firebase/util@1.4.0

Minor Changes

• a99943fe3 #5539 - Use esm2017 builds by default

Patch Changes

• b835b4cba #5506 - areCookiesEnabled could encounter runtime errors in certain enviornments

@firebase/webchannel-wrapper@0.6.0

Minor Changes

• a99943fe3 #5539 - Use esm2017 builds by default

Patch Changes

• 456d664ae #5485 - Remove an unused option (backgroundChannelTest).

@firebase/analytics@0.7.1

Patch Changes

• b835b4cba #5506 - checking isSupported led to runtime errors in certain environments

• Updated dependencies [a99943fe3, b835b4cba]:

  • @firebase/logger@0.3.0
  • @firebase/util@1.4.0
  • @firebase/component@0.5.7
  • @firebase/installations@0.5.1

@firebase/analytics-compat@0.1.2

Patch Changes

• b835b4cba #5506 - checking isSupported led to runtime errors in certain environments

• Updated dependencies [a99943fe3, b835b4cba, b835b4cba]:

  • @firebase/util@1.4.0
  • @firebase/analytics@0.7.1
  • @firebase/component@0.5.7

@firebase/app@0.7.1

Patch Changes

• Updated dependencies [a99943fe3, b835b4cba]:
  • @firebase/logger@0.3.0
  • @firebase/util@1.4.0
  • @firebase/component@0.5.7

@firebase/app-check@0.4.1

Patch Changes

• b835b4cba #5506 - AppCheck could encounter runtime errors when initialized in Node

• e62d02e52 #5540 - Check for and initialize App Check debug mode during initializeAppCheck() instead of on import.

• Updated dependencies [a99943fe3, b835b4cba]:

  • @firebase/logger@0.3.0
  • @firebase/util@1.4.0
  • @firebase/component@0.5.7

@firebase/app-check-compat@0.1.2

Patch Changes

• b835b4cba #5506 - AppCheck could encounter runtime errors when initialized in Node

• Updated dependencies [b835b4cba, e62d02e52, a99943fe3, b835b4cba]:

  • @firebase/app-check@0.4.1
  • @firebase/logger@0.3.0
  • @firebase/util@1.4.0
  • @firebase/component@0.5.7

@firebase/app-compat@0.1.2

Patch Changes

• Updated dependencies [a99943fe3, b835b4cba]:
  • @firebase/logger@0.3.0
  • @firebase/util@1.4.0
  • @firebase/app@0.7.1
  • @firebase/component@0.5.7

@firebase/auth-compat@0.1.3

Patch Changes

• Updated dependencies [a5d87bc5c, a99943fe3, 07b88e6e8, b835b4cba, 4d2a54fb0, c2362214a]:
  • @firebase/auth@0.18.0
  • @firebase/util@1.4.0
  • @firebase/component@0.5.7

@firebase/component@0.5.7

Patch Changes

• Updated dependencies [a99943fe3, b835b4cba]:
  • @firebase/util@1.4.0

@firebase/database@0.12.1

Patch Changes

• dfe65ff9b #5537 - Added an entry point @firebase/database-compat/standalone to share code with Admin SDK properly

• Updated dependencies [a99943fe3, b835b4cba]:

  • @firebase/logger@0.3.0
  • @firebase/util@1.4.0
  • @firebase/component@0.5.7

@firebase/database-compat@0.1.1

Patch Changes

• dfe65ff9b #5537 - Added an entry point @firebase/database-compat/standalone to share code with Admin SDK properly

• b79bd33e4 #5531 - export types from @firebase/database-compat for admin SDK

• Updated dependencies [dfe65ff9b, a99943fe3, b835b4cba]:

  • @firebase/database@0.12.1
  • @firebase/logger@0.3.0
  • @firebase/util@1.4.0
  • @firebase/component@0.5.7
  • @firebase/database-types@0.9.1

@firebase/database-types@0.9.1

Patch Changes

• Updated dependencies [a99943fe3, b835b4cba]:
  • @firebase/util@1.4.0

@firebase/firestore-compat@0.1.3

Patch Changes

• 08c098211 #5538 - only publish dist folder to npm for @firebase/firestore-compat

• Updated dependencies [f78ceca1c, a99943fe3, b835b4cba, a99943fe3]:

  • @firebase/firestore@3.1.0
  • @firebase/util@1.4.0
  • @firebase/component@0.5.7

@firebase/functions@0.7.2

Patch Changes

• Updated dependencies [a99943fe3, b835b4cba]:
  • @firebase/util@1.4.0
  • @firebase/component@0.5.7

@firebase/functions-compat@0.1.3

Patch Changes

• Updated dependencies [a99943fe3, b835b4cba]:
  • @firebase/util@1.4.0
  • @firebase/component@0.5.7
  • @firebase/functions@0.7.2

@firebase/installations@0.5.1

Patch Changes

• Updated dependencies [a99943fe3, b835b4cba]:
  • @firebase/util@1.4.0
  • @firebase/component@0.5.7

@firebase/installations-compat@0.1.1

Patch Changes

• Updated dependencies [a99943fe3, b835b4cba]:
  • @firebase/util@1.4.0
  • @firebase/component@0.5.7
  • @firebase/installations@0.5.1

@firebase/messaging@0.9.1

Patch Changes

• b835b4cba #5506 - checking isSupported led to runtime errors in certain environments

• Updated dependencies [a99943fe3, b835b4cba]:

  • @firebase/util@1.4.0
  • @firebase/component@0.5.7
  • @firebase/installations@0.5.1

@firebase/messaging-compat@0.1.1

Patch Changes

• b835b4cba #5506 - checking isSupported led to runtime errors in certain environments

• Updated dependencies [a99943fe3, b835b4cba, b835b4cba]:

  • @firebase/util@1.4.0
  • @firebase/messaging@0.9.1
  • @firebase/component@0.5.7

@firebase/performance@0.5.1

Patch Changes

• b835b4cba #5506 - Performance could encounter runtime errors when initialized in certain environments

• Updated dependencies [a99943fe3, b835b4cba]:

  • @firebase/logger@0.3.0
  • @firebase/util@1.4.0
  • @firebase/component@0.5.7
  • @firebase/installations@0.5.1

@firebase/performance-compat@0.1.1

Patch Changes

• b835b4cba #5506 - Performance could encounter runtime errors when initialized in certain environments

• Updated dependencies [a99943fe3, b835b4cba, b835b4cba]:

  • @firebase/logger@0.3.0
  • @firebase/util@1.4.0
  • @firebase/performance@0.5.1
  • @firebase/component@0.5.7

@firebase/remote-config-compat@0.1.1

Patch Changes

• Updated dependencies [f90c1d081, a99943fe3, b835b4cba]:
  • @firebase/remote-config@0.3.0
  • @firebase/logger@0.3.0
  • @firebase/util@1.4.0
  • @firebase/component@0.5.7

@firebase/rules-unit-testing@2.0.1

Patch Changes

• 46d26ff96 #5500 - Fix typing issues where Database/Firestore/Storage compat instances returned by RulesTestContext are not compatible with v9 modular APIs.

• 29e0be2cb #5501 - Set RTDB namespace to be same as projectId by default instead of ${projectId}-default-rtdb. This fixes rules not being applied and other issues related to namespace mismatch.

@firebase/storage@0.8.3

Patch Changes

• Updated dependencies [a99943fe3, b835b4cba]:
  • @firebase/util@1.4.0
  • @firebase/component@0.5.7

@firebase/storage-compat@0.1.3

Patch Changes

• Updated dependencies [a99943fe3, b835b4cba]:
  • @firebase/util@1.4.0
  • @firebase/storage@0.8.3
  • @firebase/component@0.5.7

[google-cla]

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.

[github-actions]

Changeset File Check ⚠️

• Changeset formatting error in following file:

  Some packages have been changed but no changesets were found. Run `changeset add` to resolve this error.
  If this change doesn't need a release, run `changeset add --empty`.
  

[google-cla]

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-cla]

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-cla]

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-cla]

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-cla]

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-cla]

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.