chore(sdk): add OrgInvitationResponse.token field (robosystems #1166) - #189
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
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.
Summary
Regenerates
OrgInvitationResponseto include the new optionaltokenfield, added upstream in robosystems #1166.Change
token: None | str | Unset = UNSETonOrgInvitationResponse. No other model changed; the diff is scoped to this one field.AUTH_INVITE_TOKEN_IN_RESPONSEis enabled in a non-production environment, and it is always null in production. It exists so automated authorization tests can complete the invite → register flow without email interception.Contract
OrgInvitationResponseis an OpenAPI-generated model, not a facade and not on the integration-template emit path; an added optional field breaks nothing. Not a stable-tier change, no deprecation, no release notes required.Sequencing
The field originates in robosystems #1166, which is open, not yet merged/deployed (prod on API 1.8.3). Because the field is optional, this client is forward-compatible against the current API — the field is simply always absent until #1166 lands. If #1166's review changes the field (e.g. excludes it from the schema), re-regenerate before publishing.