Fix device authorization polling state and add test CI - #1
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
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.
Device authorization polling returns a deadline but previously lost updated polling state, including cumulative slow_down intervals. Return an immutable updated attempt, preserve increasing intervals, reject polling at expiration, and document how callers carry state forward. Update TypeScript declarations and add regression coverage for consecutive slow_down responses and early polling.
Add PR/main test CI using commit-pinned official Actions, read-only contents permissions, and disabled persisted checkout credentials.
Validation: reviewed source and regression tests; local execution is unavailable in this session. GitHub CI must pass before merging. Returning attempt adds a field to pending results; callers using exact object comparisons must update. Old attempt reuse remains a caller responsibility and is documented. No changes to OAuth scopes, credentials, publication, or main branch settings.