chore: Merge master into dev to sync history - #782

Merged

jonathanedey merged 33 commits into

devfrom

Sep 9, 2026

jonathanedey commented Sep 8, 2026 •

edited

Loading

Contributor

This is a one time merge of master into dev to resolve history divergence caused by previous release merge commits.

NOTE:

This PR MUST be merged as as commit to ensure history is synced.
Ignore the Update Branch button. This is expected and should be ignored because dev is based off of the master branch and master contains changes not in dev. Merging this PR will resolve this.
The out of sync diffs in the release workflows will be reverted in a follow up PR.

google-oss-bot and others added 30 commits

May 21, 2020 11:49


          Merge dev into master

54b8114


          Merge dev into master

cef91ac


          Merge dev into master

77177c7


          Merge dev into master

a957589


          Merge dev into master

eb0d2a0


          Merge dev into master

05378ef


          Merge dev into master

4121c50


          Merge dev into master

928b104


          Merge dev into master

02cde4f


          Merge dev into master

6b40682


          Merge dev into master

e60757f


          Merge dev into master

bb055ed


          Merge dev into master

23a1f17


          Merge dev into master

1d24577


          Merge dev into master

61c6c04


          [chore] Release 4.12.0 (#561)

32af2b8

- Release 4.12.0


          Revert "[chore] Release 4.12.0 (#561)" (#565)

02300a8

This reverts commit 32af2b8.


          Merge dev into master

74c9bd5


          Merge dev into master

37c7936


          Merge dev into master

b04387e


          Merge dev into master

87b867c


          Merge dev into master

6a28190


          Merge dev into master

c3be6f2


          Merge dev into master

afeaa15


          Merge dev into master

570427a


          Merge dev into master

fe866a0


          Merge dev into master

db240e4


          Merge dev into master

d515faf


          Merge dev into master

26dec0b


          [chore] Release v4.19.0 (#747)

4f7026f

* chore: Added and `AGENTS.md` file to instruct AI agents how to interact with this repository (#710)

* fix(auth): Fixed auth error code parsing (#712)

* fix(auth): Fixed auth error code parsing

* fix(auth): Fixed test to use error message prefix

* chore: update copyright headers from Google Inc. to Google LLC (#713)

* chore: Update github actions workflows and integration test resources (#740)

* chore: Pinned github actions to a full-length commit SHA

* chore: Update integration test resources

* chore: Added environment label to release action

* Trigger integration tests

* feat(firestore): Added Firestore Multi Database Support (#733)

* feat(firestore): Add Firestore Multi Database Support

* fix: Address gemini review

* fix: gemini review

* fix: Update name from API review

* fix: Address review comments

* chore: Fix CONTRIBUTING.md typo

Co-authored-by: Lahiru Maramba <llahiru@gmail.com>

---------

Co-authored-by: Lahiru Maramba <llahiru@gmail.com>

* feat(auth): Add `QueryUsers` API (#727)

This change implements the accounts:query functionality, providing a new QueryUsers method that allows searching for users with filters and sorting options.

RELEASE_NOTE: Added QueryUsers() API to support querying user accounts with filters, sorting, and pagination.

* Update the release actions process (#741)

This PR refactors the release automation to improve security by removing the direct merge from the workflow.

* [chore] Release 4.19.0 (#742)

* Revert "[chore] Release 4.19.0 (#742)" (#744)

This reverts commit 3a86709.

* chore: Update Release Workflows for Push triggers (#745)

* chore: Update release actions to run on Release env

* Trigger CI

* update the actions

* update the base_ref

* remove fetch-depth to prevent conflicts

* [chore] Release 4.19.0 Take 2 (#746)

---------

Co-authored-by: Jonathan Edey <145066863+jonathanedey@users.noreply.github.com>
Co-authored-by: Lahiru Maramba <llahiru@gmail.com>

lahirumaramba added 3 commits

May 14, 2026 16:13


          Merge dev into master to resolve release divergence

aa29809


          Merge remote-tracking branch 'origin/dev'

e853b36


          Merge dev into master

eebb06f

github-advanced-security AI commented Sep 8, 2026

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

4 similar comments

github-advanced-security AI commented Sep 8, 2026

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

github-advanced-security AI commented Sep 8, 2026

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

github-advanced-security AI commented Sep 8, 2026

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

github-advanced-security AI commented Sep 8, 2026

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

gemini-code-assist Bot commented Sep 8, 2026

Contributor

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

google-cla Bot commented Sep 8, 2026

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

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

jonathanedey closed this

jonathanedey reopened this

jonathanedey requested a review from lahirumaramba

September 9, 2026 15:33

lahirumaramba approved these changes

View reviewed changes

jonathanedey merged commit 9d506cc into dev

167 of 170 checks passed

jonathanedey mentioned this pull request

chore: remove unwanted tag_release.yml and restore release.yml #783

Merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet