Repository navigation
feat(updates): move plugin updates and GitHub installs to the store - #51
Merged
Merged
Conversation
hannojg
marked this pull request as ready for review
October 27, 2026 15:00
lauridskern
added a commit
that referenced
this pull request
Oct 27, 2026
Brings in the store-based Codex updater (#51). The Claude smoke test now checks for any Codex plugin_ tool and the store banner, as the host tests do.
lauridskern
added a commit
that referenced
this pull request
Oct 27, 2026
#51 renamed the Codex update tools and replaced the update banner's buttons, so the absence checks look for plugin_ tools and the plugin store banner, as the host tests do.
lauridskern
added a commit
that referenced
this pull request
Oct 27, 2026
Brings in the store-based Codex updater (#51): the Cursor smoke test checks for any Codex plugin_ tool, and the release notes say the Claude and Cursor packages run the shared server, which has no updater.
lauridskern
added a commit
that referenced
this pull request
Oct 27, 2026
Brings in the store-based Codex updater (#51): the shared plugin smoke test checks for any Codex plugin_ tool and the store banner.
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.
Mobile Dev is now in the plugin store, but its updater still follows GitHub releases. A GitHub release can be available while the same version is waiting for store review.
This reads the published version through Codex's experimental
plugin/readAPI and opens the store listing to update. The API keeps the published and installed versions separate; the CLI listing prefers the installed version and cannot detect later store updates reliably.GitHub installations offer migration once the store has version
0.1.167or newer, and at least the running plugin version. After the user installs and enables that package, Finish migration verifies its identity and local manifest, removes the GitHub plugin and marketplace, and asks the user to restart Codex. Local recordings and saved data are preserved. Catalog failures stay quiet, and the GitHub version lookup and upgrade tool are removed.The temporary-profile smoke test exercises real Codex CLI installation and removal with simulated store state. UI tests cover opening the store, cleanup, failures and retry. The store install itself has not been tested through the new version's live listing.
Release
0.1.167on GitHub first, then submit that release's ZIP to the existing store listing. The version gate keeps migration unavailable until the store update is published. With the original repository name restored, existing GitHub users can receive this transition through their current Update button. While the old API URL redirects, version0.1.163requires a manualcodex plugin marketplace upgrade mobile-devinstead. Cleanup recognizes both official repository URLs.