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/app-check@0.2.0

Minor Changes

• 870dd5e35 #5033 - Added getToken() and onTokenChanged methods to App Check.

Patch Changes

• 5d007b8fb #5084 - Fixed so token listeners added through public API call the error handler while internal token listeners return the error as a token field.

• 5d31e2192 #5055 (fixes #5052) - Fix an error causing App Check to log HTTP status 429 errors in debug mode.

• Updated dependencies [870dd5e35, 5d007b8fb, 56a6a9d4a]:

  • @firebase/app-check-types@0.2.0
  • @firebase/component@0.5.4

@firebase/app-check-types@0.2.0

Minor Changes

• 870dd5e35 #5033 - Added getToken() and onTokenChanged methods to App Check.

Patch Changes

• 5d007b8fb #5084 - Fixed so token listeners added through public API call the error handler while internal token listeners return the error as a token field.

firebase@8.7.0

Minor Changes

• 870dd5e35 #5033 - Added getToken() and onTokenChanged methods to App Check.

Patch Changes

• Updated dependencies [870dd5e35, 5d007b8fb, 5d31e2192, 56a6a9d4a]:
  • @firebase/app-check@0.2.0
  • @firebase/auth@0.16.8
  • @firebase/firestore@2.3.8
  • @firebase/storage@0.5.6
  • @firebase/analytics@0.6.14
  • @firebase/app@0.6.28
  • @firebase/database@0.10.6
  • @firebase/functions@0.6.13
  • @firebase/installations@0.4.30
  • @firebase/messaging@0.7.14
  • @firebase/performance@0.4.16
  • @firebase/remote-config@0.1.41

@firebase/analytics@0.6.14

Patch Changes

• Updated dependencies [56a6a9d4a]:
  • @firebase/component@0.5.4
  • @firebase/installations@0.4.30

@firebase/app@0.6.28

Patch Changes

• Updated dependencies [56a6a9d4a]:
  • @firebase/component@0.5.4

@firebase/auth@0.16.8

Patch Changes

• 56a6a9d4a #5071 (fixes #4932) - Auto initialize auth-internal after auth has been initialized.

@firebase/component@0.5.4

Patch Changes

• 56a6a9d4a #5071 (fixes #4932) - Auto initialize auth-internal after auth has been initialized.

@firebase/database@0.10.6

Patch Changes

• Updated dependencies [56a6a9d4a]:
  • @firebase/component@0.5.4

@firebase/firestore@2.3.8

Patch Changes

• Updated dependencies [85f73abb5, 56a6a9d4a]:
  • @firebase/webchannel-wrapper@0.5.1
  • @firebase/component@0.5.4

@firebase/functions@0.6.13

Patch Changes

• Updated dependencies [56a6a9d4a]:
  • @firebase/component@0.5.4

@firebase/installations@0.4.30

Patch Changes

• Updated dependencies [56a6a9d4a]:
  • @firebase/component@0.5.4

@firebase/messaging@0.7.14

Patch Changes

• Updated dependencies [56a6a9d4a]:
  • @firebase/component@0.5.4
  • @firebase/installations@0.4.30

@firebase/performance@0.4.16

Patch Changes

• Updated dependencies [56a6a9d4a]:
  • @firebase/component@0.5.4
  • @firebase/installations@0.4.30

@firebase/remote-config@0.1.41

Patch Changes

• Updated dependencies [56a6a9d4a]:
  • @firebase/component@0.5.4
  • @firebase/installations@0.4.30

@firebase/rules-unit-testing@1.3.9

Patch Changes

• Updated dependencies [870dd5e35, 56a6a9d4a]:
  • firebase@8.7.0
  • @firebase/component@0.5.4

@firebase/storage@0.5.6

Patch Changes

• Updated dependencies [56a6a9d4a]:
  • @firebase/component@0.5.4

@firebase/webchannel-wrapper@0.5.1

Patch Changes

• 85f73abb5 #5099 - Added a new export for FetchXmlHttpFactory.

[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-oss-bot]

Size Analysis Report

Affected Products

No changes between base commit (56a6a9d) and head commit (04e59b4).

Test Logs

• Base (56a6a9d): https://github.com/firebase/firebase-js-sdk/actions/runs/980746028
• Head (04e59b4): https://github.com/firebase/firebase-js-sdk/actions/runs/980777673

[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.