fix: release-finalize.yml manifest-driven docs update - #118
Conversation
…st generator Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
![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: b839192cb0
ℹ️ 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 m = JSON.parse(fs.readFileSync(p, 'utf8')); | ||
| m.canonical_package_status = 'published'; | ||
| m.public_distribution_status = 'published'; | ||
| m.latest_audited_version = process.env.VER; |
There was a problem hiding this comment.
When finalizing the current 0.144.3 candidate, the manifest already has previous_stable_version set to 0.144.1 but rollback_version is still 0.143.0. This script only advances latest_audited_version before running sync-public-release-from-manifest.js, whose published README/guidance rollback command is rendered from manifest.rollback_version, so the generated docs and bundled manifest will keep telling users to roll back two releases instead of to the stable release being superseded. Capture the pre-finalize stable version into rollback_version before regenerating the docs.
Useful? React with 👍 / 👎.
1 participant
Summary
Status
Details
The release-finalize workflow previously relied on README-based extraction logic that broke when the README structure was refactored. This PR moves to manifest-driven generation instead, using
scripts/finalize-update-docs.shto re-generate README content deterministically from the canonical manifest.Testing