Release v1.55.0: Registry publication preflight - #25
Conversation
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
![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: f1c4afcc8a
ℹ️ 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".
| const lines = [ | ||
| `Registry publication preflight: ${report.status.toUpperCase()}`, | ||
| `Target: ${report.target}`, | ||
| report.serverName ? `Server: ${report.serverName}@${report.serverVersion ?? "unknown"}` : null, | ||
| `Local readiness: ${report.localReadiness.toUpperCase()}`, | ||
| `Package publication: ${report.packagePublication.toUpperCase()}`, | ||
| `Registry version availability: ${report.registryVersionAvailability.toUpperCase()}`, | ||
| `Network verification: ${networkVerification}` |
There was a problem hiding this comment.
When users run the documented default registry preflight <path> command without --json, this renderer prints only the summary and findings and never renders report.publisherPlan.steps. Consequently, the primary human-facing output omits both ordered mcp-publisher commands despite the command promising a non-executing publication plan; include the plan steps in the text report.
Useful? React with 👍 / 👎.
1 participant
Summary
Verification