The 0.1.208 carve-out lane shipped off the v0.1.207 tag (storage v8
emergency, #4677) without landing a version bump on master, so master's
package.json (0.1.207) no longer equals npm latest (0.1.208) and the
one-click release drift guard aborts (run 40520077248, step 'Drift
guard'). Version-string sync ONLY: master already carries the 0.1.208
content under its own commits (#4708 for #4677, #4666). Plugin manifests
synced via scripts/sync-codex-plugin-version.mjs (#4449) so the publish
workflows' --check gate stays green. No code change; branch deliberately
does NOT match *_release-v* so merging publishes nothing.
The four plugin manifests (.agents/plugins/marketplace.json,
.claude-plugin/marketplace.json + .claude-plugin/plugin.json,
plugins/codex/.codex-plugin/plugin.json) sat at 0.1.205 while package.json
is 0.1.207 — the #4449 gate (node scripts/sync-codex-plugin-version.mjs
--check) fails on master, so any release branch cut now would be rejected
by release.yml's pre-tag check, and the Codex/Claude marketplaces have not
offered updates since v0.1.206. Run the sync script (no code changes).
Follow-up to the Codex plugin manifest work: rebasing onto current master
bumped package.json to 0.1.205, so the four manifests that mirror it had to
move too:
- .agents/plugins/marketplace.json
- plugins/codex/.codex-plugin/plugin.json
- .claude-plugin/marketplace.json
- .claude-plugin/plugin.json
This is exactly the drift the sync script exists to catch: before the script
existed, .claude-plugin/ still said 0.1.188 while package.json said 0.1.204,
which is what makes Codex's plugin page report a stale version.
No behavioral change; `node scripts/sync-codex-plugin-version.mjs --check`
now passes.