docs(changelog): add v0.3.0 entry and bump marketplace plugin version - #38
Open
bmadcode wants to merge 1 commit into
Open
docs(changelog): add v0.3.0 entry and bump marketplace plugin version#38bmadcode wants to merge 1 commit into
bmadcode wants to merge 1 commit into
Conversation
Covers #37, the uv run conversion. Marketplace plugin version goes 0.2.0 -> 0.3.0; nothing in the release workflow touches marketplace.json, so it drifts from package.json unless bumped by hand (it was already a patch behind at 0.2.0 against package.json 0.2.1).
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
WalkthroughThe plugin version changes to ChangesRelease metadata
Estimated code review effort: 1 (Trivial) | ~5 minutes Poem
🚥 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 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release notes for v0.3.0, covering #37.
Changelog
One release, one change: skills stop shelling out to a bare
python3. The entry explains why it mattered rather than just naming the swap — the failure was silent. Below Python 3.11 the resolver hard-exits ontomllib, and each skill's "if the script fails" path caught it and hand-merged the TOML layers in-context. A run could resolve customization subtly wrong and look completely fine.Version bump
Marketplace plugin
0.2.0→0.3.0.Worth knowing: it was already drifting.
package.jsonwas at0.2.1whilemarketplace.jsonstill said0.2.0, because nothing in the release workflow touches that file. Compare with bmad-method-test-architecture-enterprise, which has aSync marketplace versionstep inpublish.yamlplus atest-release-metadata.jsguard that fails the suite when the two disagree. That pattern is worth copying here — it would have caught this drift automatically.package.jsonis left alone; the release workflow owns it.Verification
markdownlint and prettier pass. All 10 marketplace skill paths resolve to a real
SKILL.md.Summary by CodeRabbit
uv.uv run.