Skip to content

docs: drop the stale marketplace pin step from the release guide #102

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
milanagm merged 2 commits into from
Sep 24, 2026
Merged

docs: drop the stale marketplace pin step from the release guide #102

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
80a031b
removed outdated point
milanagm Sep 24, 2026
0fe04eb
docs: drop the blank line left behind by the removed release step
milanagm Sep 24, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -70,8 +70,6 @@ tsdown bundles the hook and its runtime dependencies into `plugins/tracing/dist/

4. Review and publish the draft GitHub release created by the workflow.

5. Point `.agents/plugins/marketplace.json` at the new version, because that pin is what users install.

Do not approve the npm package or publish the GitHub draft until both staged artifacts have been reviewed. If the workflow fails before staging, fix the problem and move the tag to the corrected release commit. If staging succeeded, do not rerun the workflow with the same version, because staged and published versions cannot be staged again.

The two versions you bump matter for different things. The one in `package.json` only decides which tarball npm hands out. The one in `plugin.json` is the version Codex installs under, so it names the cache directory `~/.codex/plugins/cache/<marketplace>/<plugin>/<version>/` and therefore decides whether an existing install is refreshed at all. Never leave `version` out of `plugin.json`, because Codex then installs under the literal name `local`, and since that name always matches itself, no automatic refresh will ever replace the install.
Loading