v0.5.0 feat: add cross-device OAuth login - #10
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
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
anyapi loginstart RFC 8628 device OAuth for immediate cross-device account sign-in.anyapi login --api-keyas the local manual-key path and keepanyapi connectas the trial-upgrade PKCE flow.0.5.0with updated bundled onboarding guidance.Test coverage
git diff --checkpass.Pre-landing review
Three independent review passes are clean after fixes. The reviews specifically checked RFC 8628 behavior, refresh-token lifecycle, API-key isolation, legacy config migration, endpoint fallback, and release ordering.
Documentation
README, changelog, and the bundled onboarding skill describe the new login path and its distinction from trial upgrade and manual-key storage.
Test plan
npm testnpm run buildnode dist/index.js login --helpgit diff --check