Repository navigation
fix(updates): read store versions without CLI authentication - #71
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
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.
In #51, store update checks started querying
plugin/readthrough a separate Codex app-server. When the CLI uses API-key authentication, it rejects that lookup before making the HTTP request, so the migration banner never appears even after the matching store release is public.Read Mobile Dev's public store endpoint directly without credentials and validate its identity, enabled status and
release.version. Keep installed versions and enablement checks in the local CLI inventory, with the package manifest checked before GitHub cleanup. Scope available-plugin discovery to our Git marketplace: the unfiltered response was 4.1 MB and exceeded the runner's 1 MB limit. Existing update timings and migration error tags are preserved, with bounded failure categories added for checks. The version is bumped to0.1.171.I ran the changed updater in isolation on both Macs against the real store and CLI. The API-key Mac now returns
migrationfor its installed0.1.169without changing its login. All 24 focused tests and the real-CLI migration smoke test pass. The broader local suite has 921 passes and one failure because the fresh worktree has no built Baguette binary; CI runs the shared checks on Linux and skips that macOS-only test.