Require explicit plaintext auth storage - #47
Merged
Merged
Conversation
Default OAuth credential persistence now fails safely when the system keychain is unavailable, while explicit file mode supports headless environments with clear plaintext warnings.
jlitola
force-pushed
the
golden-adasaurus
branch
from
April 29, 2026 06:28
bb344e2 to
7bedd9c
Compare
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.
Summary
config.tomlauth storage mode with keychain default and explicitfilemode for plaintext OAuth storage.~/.githitsmigration and logout cleanup.Verification
bun testbun run typecheckbun run build