Repository navigation
chore: release v1.0.2 - #183
Merged
Merged
Conversation
Bundles the token-lifetime fixes since 1.0.1: - accept numeric-string OAuth fields so refresh no longer runs every poll (#178) - per-error refresh backoff, transient failures retry next poll (#178) - failed refresh reason logged once as a warning (#178) - poll loop rebuilt immediately after re-authentication (#175) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Release v1.0.2, bundling the token-lifetime fixes accumulated since 1.0.1.
Changelog
expires_in) as strings, which the token normalizer dropped, so no expiry could be derived and the token looked permanently near-expiry. Numeric strings are now coerced (Access token is refreshed on every poll again (cf. #46); a failed refresh stops telemetry for 75 minutes #178).Version bumped in
package.json+io-package.json, changelog moved from WORK IN PROGRESS to the1.0.2section,io-package.jsonnews populated (all languages). Tagv1.0.2will be pushed after merge to trigger the npm deploy.