test: protect experimental package status contract - #162
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe release-version test now checks that ChangesRelease changelog contract
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
ESLint install timed out. The project may have too many dependencies for the sandbox. Comment |
|
@coderabbitai full review |
✅ Action performedFull review finished. You're currently rate limited under our Fair Usage Limits Policy. Your recent PR review activity is in the 95th percentile or higher among CodeRabbit users, so adaptive limits apply. Your next review will be available in 10 seconds. |
|
@coderabbitai full review |
✅ Action performedFull review finished. |
Closes #161
Why
The release-artifact test claimed to retain Miftah's experimental package status but did not assert the canonical changelog wording.
Change
Adds one focused
CHANGELOG.mdassertion to the existing release-version contract. Production documentation and release behavior are unchanged.Validation
npx vitest run tests/release-version.test.ts --reporter=dotnpm run lintnpm run typecheckTDD evidence: without the new assertion, the focused suite passed after a controlled removal of
Miftah is experimental and pre-1.0; with the assertion it failed as expected; restoring the existing canonical text makes it pass.Summary by CodeRabbit