Repository navigation
fix: update LongBridge heartbeat evidence action source - #603
Merged
Merged
Conversation
Co-Authored-By: Codex <noreply@openai.com>
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.
The previous QRS action pin includes tracked host-specific node_modules symlinks in its source archive, which can prevent GitHub from initializing the action snapshot. Adopt the repaired QRS source commit
2eef9296e1ca5c214213ec71a74059cf1d5014d9.This changes one
usesSHA in the existing execution-report heartbeat workflow. The action and projection implementation blobs are unchanged; package manifests, lockfiles, frozen dependency resolution, permissions, conditions, schedule, matrix and business steps remain unchanged.Validation reused for this exact candidate:
Natural CI results are reported in this PR's checks. No workflow rerun, dispatch, deployment or live heartbeat is requested. This PR does not establish consumer action download/extraction or heartbeat recovery; adoption and runtime verification remain separate decisions.