Repository navigation
Serialize expiring agent tokens and release 26.10.3 - #83
Merged
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
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.
Minting an agent token with its typed
datetimeexpiry raisedTypeErrorbefore HTTP dispatch. Serialize this request in JSON mode so the expiry reaches the service as an ISO 8601 string while omitted fields and scope grants retain their behavior. The release stamps server and SDK metadata as 26.10.3 and adds bounded-expiry guidance.Validation: two UTC/offset cases reproduce the old HTTP-encoding failure; all 61 SDK tests pass. Independent fresh installed-wheel tests pass all 61 cases with exact package source hashes. Actual owned local Canon TCP mint, list and revoke preserve the expiry and workspace scope. No server business logic, framework pin or migration changes; published 26.10.2 assets remain immutable.