mirror of
https://github.com/EveryInc/compound-engineering-plugin.git
synced 2026-10-26 16:15:28 +01:00
Trevin ChowandClaude Opus 4.7
9117c68fd9
`.claude-plugin/plugin.json` was manually bumped 3.0.3 → 3.0.4 → 3.0.5 → 3.0.6 → 3.0.7 across recent feature commits (1f20c384,f8720da3,22d493b1,47350c3e) without corresponding bumps to `.cursor-plugin`, `.codex-plugin`, the release-please manifest, or the linked cli package.json. AGENTS.md "Versioning Requirements" explicitly forbids manual bumps here — release-please owns all three plugin.json files via extra-files in .github/release-please-config.json, and the linked-versions plugin keeps cli and compound-engineering in lockstep. Drift broke `release:validate` on every PR's CI (PR #677 surfaced it). Recovery uses the "forward" path (sync everything to 3.0.7) instead of reverting .claude-plugin to 3.0.3, because developers running compound-engineering from a local main checkout already have 3.0.7 installed. Reverting would orphan their cache dirs and trigger version-regression warnings in tooling that treats the field as monotonic. Forward-sync preserves semver monotonicity with zero regression for any current install. Changes: - .cursor-plugin/plugin.json: 3.0.3 → 3.0.7 (compound-engineering extra-file) - .codex-plugin/plugin.json: 3.0.3 → 3.0.7 (compound-engineering extra-file) - .github/.release-please-manifest.json: compound-engineering 3.0.3 → 3.0.7 - .github/.release-please-manifest.json: . (cli, linked-versions) 3.0.3 → 3.0.7 - package.json: 3.0.3 → 3.0.7 (cli extra-file, linked to compound-engineering) `bun run release:validate` now reports in-sync metadata. The next release-please run will compute 3.0.8+ from a coherent starting point. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>