Merge v4.y back into master #447
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Test on ruby 2.7.0
Document watch and upcoming changes
fix Ruby 2.7 deprecation warnings
bump recursive-open-struct for Ruby 2.7 compatibility
Add userinfo.email to default scopes in gcp auth provider
These changes were backported to v4.y branch (all from master except #355). Planning to also merge this to master.
Release 4.7.0
Collaborator
Author
|
Diff on Github is misleading, specifically the README changes it shows are already on master (#436), it's confused by cherry-picks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Forked from master to cherry-pick compatible changes #446 without waiting for 5.0.
Want to merge back to minimize divergence (and the changelog will be relevant for 5.0 too)