chore(release): prepare v0.1.1 - #45
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
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 updates package and MCP version metadata to 0.1.1, documents the release additions and fixes, and adds tests validating version consistency and required release documentation. ChangesRelease alignment
Estimated code review effort: 2 (Simple) | ~10 minutes Poem
Caution Pre-merge checks failedPlease resolve all errors before merging. Addressing warnings is optional.
❌ Failed checks (2 errors)
✅ Passed checks (3 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
|
@coderabbitai review |
✅ Action performedReview finished.
|
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@CHANGELOG.md`:
- Line 12: Complete the npm release gate by verifying the trusted-publishing and
OIDC workflow configuration, confirming the tagged v0.1.1 release publishes with
provenance, and deprecating npm version 0.1.0 with a message directing users to
>=0.1.1 after publication.
In `@tests/release-version.test.ts`:
- Around line 10-19: Update releaseNotes to match the complete release heading
at the start of a line, requiring the version followed by a YYYY-MM-DD date
instead of only the “## [version] - ” prefix. Use the validated heading when
locating the entry, while preserving the existing error and section extraction
behavior.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 5e3e5455-38ac-4284-99f6-19f8fb8e0c37
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (5)
CHANGELOG.mdpackage.jsonsrc/mcp/server/miftah-server.tssrc/upstream/upstream-process-manager.tstests/release-version.test.ts
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
@coderabbitai review |
✅ Action performedReview finished.
|
Summary
@lubab/miftahv0.1.1 and keep MCP handshake identities aligned with the package version.Validation
npm run lintnpm run typechecknpm testnpm run buildnode dist/cli/main.js schemanpm run check:packRelease gate
This PR prepares the release but does not publish or deprecate a package. Before the reviewed
development->mainrelease PR is merged, configure npm trusted publishing formohanagy/miftah,.github/workflows/publish.yml, and thenpmenvironment. After the tagged GitHub release publishes from CI with provenance, deprecate npm0.1.0in favor of>=0.1.1.Relates to #6.
Summary by CodeRabbit
New Features
Bug Fixes
Chores