chore(ci): pin build lock v1.8.3 - #6
Merged
Merged
Conversation
Author
|
Cursor (@cursor) review exact commit 8044cb5 for immutable pin completeness, version-contract parity, and workflow regressions. Report exact zero if none. |
Author
|
copilot-pull-request-reviewer review exact commit 8044cb5 for immutable pin completeness, version-contract parity, and workflow regressions. Report exact zero if none. |
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 8044cb5. Configure here.
Copilot stopped work on behalf of
Eli Pinkerton (wallstop) due to an error
July 16, 2026 20:50
Eli Pinkerton (wallstop)
marked this pull request as ready for review
July 16, 2026 20:56
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Why
v1.8.3 narrowly retries GitHub's branded transient HTML HTTP 400 interstitial. Ordinary JSON HTTP 400 responses remain fail-fast. This addresses the live acquire failure observed in IshoBoy run
29529885195, which never acquired or activated Unity.Verification
Note
Low Risk
Version-pin-only change to external CI actions and matching contract constants; no application or lock-semantics edits in this repo.
Overview
Bumps the ambiguous-organization-build-lock composite actions from v1.8.2 to v1.8.3 (immutable SHA
59a2fa98…) everywhere the Windows build workflow acquires, releases, and preflights the org Unity lock.The contract verifier in
verify-resource-cleanup-contract.mjsis updated to expect the same SHA so RC014/RC017 checks stay aligned with the workflow pins. Lock inputs, FIFO/schema-5 lifecycle, runner preflight, and cleanup proof behavior are unchanged—only the pinned action version moves forward to pick up v1.8.3’s handling of GitHub’s transient HTML HTTP 400 interstitials during acquire.Reviewed by Cursor Bugbot for commit 8044cb5. Bugbot is set up for automated code reviews on this repo. Configure here.