Repository navigation
release: autter 2.2.1 — stop refreshing a dead login token - #75
Merged
Merged
Conversation
### Fixed - A refused refresh token (invalid_grant / login_required) is recorded and no longer retried until `autter login` stores new credentials (#74). - One notice per refusal instead of a warning every daemon tick. - Stored credentials are replaced only if they still hold the refresh token that was sent. - OAuth errors keep error, error_code and login_required. Co-Authored-By: Claude Opus 5.5 <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
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.
Releases #74 (CE-20). Merging this bumps the version to 2.2.1:
tag-release.ymltagsv2.2.1on the merge commit and dispatchesrelease.yml, which builds the binaries and publishes@autter/clito npm.Changes
Cargo.toml,Cargo.lock:autter2.2.0 → 2.2.1 (lockfile checked withcargo metadata --locked)npm/package.json: 2.2.0 → 2.2.1 (release.yml also stamps the tag's version)CHANGELOG.md:[2.2.1]entry for the dead-token fixWhy
About 5 installs (CLI 1.6.9–2.2.0) keep refreshing a refresh token the server has refused, every daemon tick, so those developers stay logged out and their AI-authorship data never arrives. The server side (autter-monorepo #513) already makes the refusal terminal and cheap; these installs stop only once they run a CLI with #74.
After release
autter upgradeor the background update check; affected users then runautter loginonce, which the new CLI tells them to do.stats count(*) by tokenHashPrefix, cliVersion, installId) should show refusals only from versions below 2.2.1.🤖 Generated with Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need.