feat: [DIREGAPIC] Update API definitions#995
Merged
vchudnov-g merged 1 commit intogoogleapis:masterfrom Mar 18, 2025
Merged
Conversation
Contributor
|
Do not merge yet until we can figure out the CI failures in this repo. |
vchudnov-g
approved these changes
Mar 14, 2025
Contributor
|
CI issue fixed, but re-added |
7cb1861 to
7857004
Compare
7857004 to
129eed0
Compare
129eed0 to
97a3d83
Compare
97a3d83 to
2a05abd
Compare
2a05abd to
23da3d6
Compare
23da3d6 to
d42b205
Compare
d42b205 to
8d4b5f6
Compare
8d4b5f6 to
6224a67
Compare
6224a67 to
5e15c27
Compare
5e15c27 to
a7764d3
Compare
a7764d3 to
9ce70a7
Compare
9ce70a7 to
aeca0cd
Compare
vchudnov-g
approved these changes
Mar 18, 2025
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
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.
feat: Update Compute Engine API to revision 20250302
This fixes the name of an internal proto message that could not be used previously, as per external issue b/323357483.
Generator owners: This is technically a breaking change but is being introduced without a new major version as we believe that customers are unlikely to be using the problematic field, and that it's in the best interests of most customers to keep to a minor release (see b/345025532#comment21 internally). We suggest putting a message like the following in the most appropriate place(s) for your language (version history, release notes, etc.):
This is technically a breaking change but is being introduced without a new major version as we believe that customers are unlikely to be using the problematic field, and that it's in the best interests of most customers to keep to a minor release. (We completely acknowledge that this is a breaking change, and we apologize if users are affected by it. Please [raise an issue](INSERT-LINK) with any concerns - we're keen to improve this balance where we can.)