firebase
Upgrade firebase-admin and google/cloud-firestore in rules-unit-testing yarn lock
This change is automatically done when running yarn test in the repo. We should probably check it into the repo?
The version of google-cloud/firestore in the rules-unit-testing/functions/yarn.lock was listed as '6.6.0', when it was actually pulling '6.8.0'. This change upgrades the listed version to be the real version.
🦋 Changeset detected
Latest commit: ae841d6636db9c4279877783bd7c5c15d461a2e9
The changes in this PR will be included in the next version bump.
This PR includes changesets to release 1 package
| Name | Type |
|---|---|
| @firebase/rules-unit-testing | Patch |
Not sure what this means? Click here to learn what changesets are.
Click here if you're a maintainer who wants to add another changeset to this PR
![changeset-bot[bot] avatar](https://avatars.githubusercontent.com/in/28616?v=4 "Published by a pub.dev verified publisher"){kind=small}
Changeset File Check :white_check_mark:
- No modified packages are missing from the changeset file.
- No changeset formatting errors detected.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Size Report 1
Affected Products
No changes between base commit (a90255a) and merge commit (544095e).Test Logs
- Base (a90255a): https://github.com/firebase/firebase-js-sdk/actions/runs/9391103140
- Merge (544095e): https://github.com/firebase/firebase-js-sdk/actions/runs/9391110701
Size Analysis Report 1
Affected Products
No changes between base commit (a90255a) and merge commit (544095e).Test Logs
- Base (a90255a): https://github.com/firebase/firebase-js-sdk/actions/runs/9391103140
- Merge (544095e): https://github.com/firebase/firebase-js-sdk/actions/runs/9391110701
This looks like it changes the admin SDK version, too. If that's a dev dependency then that's fine, but if not then we should add a changeset to this PR.
This looks like it changes the admin SDK version, too. If that's a dev dependency then that's fine, but if not then we should add a changeset to this PR.
Looks like it isn't a dev dependency, so I added a changeset 👍
It looks like there's a ghost entry in the toc in master that's causing our doc change check to fail. #8300 should fix
Edit: this has been fixed, CI is good now