ci(e2e): repin act runner image to current upstream digest - #480
Merged
Merged
Conversation
Signed-off-by: cascade-bot <cascade-bot@users.noreply.github.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 e2e act runner image pin was re-resolved to the current ghcr.io/catthehacker/ubuntu:act-latest digest so it stays ahead of any upstream garbage-collection window.
Was: sha256:2f22a801c486881e278401813586faf73fac7dd1d016cbe9e01122ef14a57850
Now: sha256:c710431fbad9eb3bcb102d04e5ff74fbd0ce6e383f78afebfb3770a1a817fdf9
The resolver confirmed the new image still carries Node >= 24 and that the e2e module builds against it. Add this to the merge queue so the e2e suite runs before merge.