fix: harden auth token refresh - #51
Merged
Merged
Conversation
jlitola
force-pushed
the
neat-coreopsis
branch
2 times, most recently
from
April 29, 2026 14:16
00c4ee6 to
6fd9c73
Compare
Preserve refresh tokens when providers omit rotation, recover long-running MCP servers from externally refreshed credentials, and serialize auth storage updates across parallel agents.
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
AUTH_REQUIREDguidance and no stack traces.Verification
bun testbun run typecheckbun run buildbun run dev --helpsucceeds.GITHITS_API_TOKEN=dummy GITHITS_DISABLE_UPDATE_CHECK=1 bun run dev auth statussucceeds.GITHITS_API_TOKEN=dummy GITHITS_DISABLE_UPDATE_CHECK=1 bun run dev search "router" --in npm:express --limit 1reaches backend and fails cleanly withAuthentication requiredand no stack trace.Notes
bun run dev auth statuswithoutGITHITS_API_TOKEN) hung on this machine while accessing local OAuth storage, so I did not claim a successful real refresh smoke. The refresh behavior is covered by focused token-manager/auth-service tests.