chore!: bump authorizer-proto-go to v0.2.0-rc.1 - #29
Merged
Conversation
Picks up the id-only DeleteUserRequest from authorizerdev/authorizer#753. No call-site change is needed: DeleteUser passes *authorizerv1.DeleteUserRequest straight through and nothing in this repo constructs the message, so the field rename is entirely inside the generated package. BREAKING CHANGE: callers must build DeleteUserRequest with Id instead of Email. Requires server 2.4.0+.
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
1 participant
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.
Picks up the id-only
DeleteUserRequestfrom authorizerdev/authorizer#753, released as authorizer-proto-go v0.2.0-rc.1.Why this is a dependency bump and nothing else
DeleteUserpasses*authorizerv1.DeleteUserRequeststraight through to GraphQL/REST/gRPC, and nothing in this repo constructs the message — no test, README, or example. So the field rename lives entirely inside the generated package.I verified that rather than assuming it, before the release existed: built and vetted this repo against the regenerated stubs via a local
replacedirective. Both exited 0, andgo testfailures were byte-identical to baseline (they need a live server with valid client config — pre-existing, unrelated).BREAKING
Callers must build the request with
Idinstead ofEmail:Requires server 2.4.0+. The server removed the field rather than accepting both.
Verified against the real published module
go buildandgo vetboth exit 0, and I checked the resolved module in the module cache rather than trusting the version string:func (x *DeleteUserRequest) GetId() string— presentfunc (x *DeleteUserRequest) GetEmail() string— gone (0 matches)