fix(fleet): correct the register-run upload-artifact pin to the real v4.6.2 sha - #275
Merged
Merged
Conversation
…v4.6.2 sha Signed-off-by: Joshua Temple <joshua.temple@stablekernel.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
1 participant
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 register-run composite action pinned actions/upload-artifact to a non-existent SHA (de65e23a..., commented v4.6.2), so every fleet suite that registers a run failed at Set up job with 'Unable to resolve action ... unable to find version'. actionlint cannot verify SHA existence, so only the live rc.27 fleet run caught it. Correct the pin to the real v4.6.2 SHA ea165f8d... (already used elsewhere in this repo). Fleet infra only.