feat: prepare for iso deprecated field removal #320
Merged
Conversation
This file contains 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
jooola
force-pushed
the
iso-deprecated-field-removal
branch
from
c4af68c to
f71b482
Compare
jooola
force-pushed
the
iso-deprecated-field-removal
branch
from
f71b482 to
77d0a34
Compare
apricote
approved these changes
Oct 23, 2023
jooola
pushed a commit
that referenced
this pull request
Oct 23, 2023
🤖 I have created a release *beep* *boop* --- ## [1.31.0](v1.30.0...v1.31.0) (2023-10-23) ### Features * prepare for iso deprecated field removal ([#320](#320)) ([beae328](beae328)) ### Dependencies * update pre-commit hook psf/black-pre-commit-mirror to v23.10.0 ([#319](#319)) ([184bbe6](184bbe6)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
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.
Continuation of #318