chore(changeset): catch-up changesets for 6 untracked v1.9.0 fixes - #1640
Conversation
Six user-facing fixes merged after v1.8.0 without a changeset, so they would ship in v1.9.0 with no changelog entry and their authors uncredited. All are patch fixes; the release target stays at 1.9.0. Covers: #1637, #1607, #1632, #1616, #1612, #1523. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
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 selected for processing (6)
📝 WalkthroughWalkthroughSix patch changesets document existing behavior changes for archive spacing, CLI root validation, config-picker labels, schema YAML fidelity, canonical schema roots, and task-numbering warnings. ChangesPatch release notes
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related issues
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 |
alfred-openspec
left a comment
There was a problem hiding this comment.
All six source PRs are merged, the catch-up entries preserve the original contributor credits, and a fresh Changesets dry run keeps the release at v1.9.0. Full CI is green. Tiny non-blocking description nit: the generated release currently contains 16 changesets, not 17.
Status
Ready for review. Adds only
.changeset/*.mdfiles — no code changes.What was missing
Six user-facing fixes merged after v1.8.0 without a changeset. As-is, the v1.9.0 Version Packages PR (#1629) would ship them with no changelog entry, and three external contributors would go uncredited:
## Requirementswhen syncing specsupdateworkflow; drop "expanded-profile" wordingWhat it does
Adds one patch changeset per fix, each with a user-focused description and a manual
Thanks @authorcredit + PR link (since the changeset is authored here, not in the original PR).Proof it's safe
changeset statusstill resolves@fission-ai/openspecto minor → 1.9.0 — the release target is unchanged; this only fills in the changelog.Next step
Once merged, the Changesets action regenerates the Version Packages PR (#1629) to include all 17 items. Then #1629 can be approved and merged to publish v1.9.0.
🤖 Generated with Claude Code
Summary by CodeRabbit
spec.mdnow preserves blank lines around the Requirements heading.--store, with consistent JSON error diagnostics.