Repository navigation
Sync SDK skills with MCP verification flow - #5
Conversation
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: 42cb3b4176
ℹ️ 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": "@proofable/sdk", | ||
| "version": "0.1.5", | ||
| "version": "0.1.6", |
There was a problem hiding this comment.
When this version is tagged and published, CHANGELOG.md will still jump from Unreleased directly to 0.1.5, so users upgrading to 0.1.6 will have no record of the newly documented external-signer verification flow. This is a user-facing packaged-skill change, and the repository's PR template requires such changes to be recorded under Unreleased; add and link the 0.1.6 release entry as part of this version bump.
Useful? React with 👍 / 👎.
1 participant
Change
Sync SDK skill projections and candidate package version for the explicit MCP signing flow.
Evidence
ssot:release-gate.Acceptance boundary
Coordinate publication with the accepted MCP server and public package release.