forked from openclaw/openclaw
-
Notifications
You must be signed in to change notification settings - Fork 0
ci(build-stable): fix release-check manifest source #83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
ryan-dyer-sp
wants to merge
2
commits into
brightfire/ci
from
claw/vash/fix-release-check-manifest-source
Closed
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the
bf-build-stableworkflow, the manifest that drives the build is copied and parsed near the start (.github/workflows/bf-build-stable.yml:70-86), but the workflow later refreshesorigin/brightfire/*before this script runs (.github/workflows/bf-build-stable.yml:112). Ifbrightfire/ciadvances during the long build/test phase, this moving default reads the newer manifest instead of the manifest that produced the current stable tree, so the release gate can skip or write a fingerprint for patches that were not actually built. Pass a pinned ref/blob or the staged manifest hash from the parse step instead of rereadingorigin/brightfire/ci.Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch — fixed in 9849462.
The race is real even with
concurrency: cancel-in-progress: cancel signals aren't instant, and the workflow has an interveninggit fetch origin '+refs/heads/brightfire/*:refs/remotes/origin/brightfire/*'step that advancesorigin/brightfire/cimid-run. Worse, since the fingerprint writer also reads from the (re-read)manifest_sha256output, a mid-build push would have made us publish a fingerprint claiming to represent a manifest the build never actually saw.Fix: the "Fetch patch manifest" step now also stages a frozen copy to
/tmp/BRIGHTFIRE_PATCHES.pinned.mdand records its sha256 toGITHUB_ENV.check-release-needed.shacceptsPINNED_MANIFEST_PATH/PINNED_MANIFEST_SHA256and prefers them; it falls back to theMANIFEST_REFgit read (with a warning) for local invocations. Same sha now flows into both the gate comparison and the published fingerprint asset.Verified all three branches manually (pinned + pre-sha, pinned + auto-sha, missing-pinned fallback). +70/-23 across the workflow and the script.