Repository navigation
Fix Orion release validation for Blue v4.4.0 manifest - #468
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: cd62705383
ℹ️ 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".
| @@ -1 +1 @@ | |||
| 2.0.2 | |||
| 2.0.3 | |||
There was a problem hiding this comment.
When this fix is tagged as v2.0.3, the release workflow derives BASE_VERSION=2.0.3, but CHANGELOG.md still ends at 2.0.2; consequently scripts/extract-changelog.sh returns an empty body and .github/workflows/release.yml deliberately publishes the release with empty notes. Add a 2.0.3 changelog section so users can see why this replacement release exists.
Useful? React with 👍 / 👎.
The v2.0.2 release failed before building Orion because Blue v4.4.0's published runtime manifest contains
source_digestbut nosource_revision. Read the digest from that manifest, resolve the Blue release tag to its commit, and require it to match the pinned module revision before building. Bump Orion to v2.0.3 so the failed v2.0.2 tag remains immutable.Validation: parsed release.yml, checked the embedded Bash step with
bash -n, verified the published Blue manifest digest format and tag target, and rangit diff --check. The release build remains the publishing gate.