Repository navigation
chore: prepare mcporter 0.15.0 release - #451
Conversation
|
🦞👀 Pull request received. I will update this pull request when review starts. |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 26ecbc37a7
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| { | ||
| "name": "mcporter", | ||
| "version": "0.14.3", | ||
| "version": "0.15.0", |
There was a problem hiding this comment.
After this bump, the credential-free release example in docs/RELEASE.md:33 still sends -f tag=v0.14.3 (the local gh workflow run --help confirms that -f passes the raw key=value input). In the checked .github/workflows/release.yml:45-59, dry-run validation accepts only an empty tag or v${package.json.version}, so anyone following the documented 0.15.0 rehearsal command fails before the build and test jobs run; update the example alongside this release.
Useful? React with 👍 / 👎.
1 participant
Prepare mcporter 0.15.0 with all seven Unreleased entries preserved verbatim and reordered to lead with keeping healthy MCP servers available when another server fails.
This is a minor release because the release workflow adds a manual
dry_runoption and the documentation adds runnable MCP integration examples. It also includes inline ad-hoc argument handling, dependency updates, and release rehearsal fixes. There are no new security-fix claims in these entries.Validation: independent Codex autoreview; exact-head CI and the documented release gates are required before tagging. After merge, run the Actions dry run against the merge commit, then the local Developer ID/notarization gate and protected draft verification before Actions publishes npm and updates Homebrew. Restore the next patch Unreleased stub after verified publication, as documented.