docs(changelog): add v6.11.0 entry and sync marketplace.json - #2705
docs(changelog): add v6.11.0 entry and sync marketplace.json#2705bmadcode wants to merge 1 commit into
Conversation
Covers 61 merged PRs since v6.10.0: 12 breaking changes, 18 features, 18 fixes, 4 removals. #2587 and #2598 are omitted as a land-then-revert pair with net-zero effect. marketplace.json had drifted. Its six plugin versions were still 6.10.0 — nothing in publish.yaml touches this file, so the drift is chronic (v6.8.0 shipped it at 6.6.0, v6.9.0 and v6.10.0 at 6.8.0). All six now read 6.11.0. The lifecycle plugin also listed six deprecated skills: bmad-quick-dev, bmad-create-story, bmad-dev-story, bmad-sprint-status, bmad-document-project, and bmad-generate-project-context. A published plugin should expose current skills, not forwarding shims, so they are removed and bmad-project-context is added in their place. Note this means the "old IDs keep working through a shim" guarantee holds for module installs but not for plugin-marketplace installs. Skills arrays are sorted by path, which groups them agents -> plan -> ship -> core-skills and makes drift like this easier to spot.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe marketplace manifest updates plugin versions from 6.10.0 to 6.11.0. It also revises the ChangesMarketplace configuration
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Release notes for v6.11.0 — a minor bump. Twelve breaking changes, but the repo reserves shim removal for the v7 cut, so every retired ID still resolves.
Covers 61 merged PRs since
v6.10.0. #2587 and #2598 are omitted as a land-then-revert pair with net-zero effect. Each entry was written from the closed PR rather than the merge subject.The entry
12 breaking changes · 18 features · 18 fixes · 4 removals, under a four-paragraph headline:
bmad-sprint-planning → bmad-build → bmad-code-reviewagents / plan / shiptree, and ~1,900 more lines deleted than added across 560 filesIncludes two entries for #2704, which is open alongside this PR.
marketplace.json
Two problems, both fixed here.
Versions had drifted. All six plugins still read
6.10.0. Nothing inpublish.yamltouches this file —npm versionwritespackage.jsononly — so the drift is chronic, not a one-off:v6.8.0shipped the marketplace at6.6.0, and bothv6.9.0andv6.10.0shipped it at6.8.0. All six now read6.11.0.The lifecycle plugin listed six deprecated skills —
bmad-quick-dev,bmad-create-story,bmad-dev-story,bmad-sprint-status,bmad-document-project,bmad-generate-project-context. A published plugin should expose current skills, not forwarding shims. Removed, withbmad-project-contextadded in their place (31 → 25 skills).Skills arrays are also sorted by path, which groups them
agents → plan → ship → core-skills. That loses the previous rough workflow ordering, in exchange for making drift like this obvious.Verification
Every path in
marketplace.jsonresolves to a realSKILL.md; no shim or husk remains in any of the six plugins; membership is unchanged by the sort.npm run validate:skillspasses (49 skills).npm testpasses.Follow-up worth considering
A CI guard so plugin versions can't drift from
package.jsonagain. I'd put it inqualityas a check that fails on mismatch, rather than an auto-rewrite inpublish.yaml— the version-bump commit happens after tests run, so a rewrite there would land unverified.Once this merges, the release is triggered manually: