From 80a031b86db2f089c3d4416b839006ab04912b67 Mon Sep 17 00:00:00 2001 From: Milana Gurbanova Date: Thu, 24 Sep 2026 09:25:48 +0200 Subject: [PATCH 1/2] removed outdated point --- CONTRIBUTING.md | 1 - 1 file changed, 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index a45398d..8ba588f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -70,7 +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. From 0fe04ebd0aed46f0a30d23a544b4dcc2613f4cef Mon Sep 17 00:00:00 2001 From: Milana Gurbanova Date: Thu, 24 Sep 2026 09:28:07 +0200 Subject: [PATCH 2/2] docs: drop the blank line left behind by the removed release step --- CONTRIBUTING.md | 1 - 1 file changed, 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 8ba588f..a35ec5b 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -70,7 +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. - 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////` 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.