You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a good practice that ensures reproducible builds and avoids potential security issues.
In our case 0c45773b623bea8c8e75f6c82b208c3cf94ea4f9 is the sha1 for v4.0.2 which, if I'm not mistaken, should not fail the build as it is recent enough. But this failed the build.
The text was updated successfully, but these errors were encountered:
Following this annoucement, workflows automatically fail for old versions of this action.
In our workflow we reference versions by sha1 rather than by tag:
This is a good practice that ensures reproducible builds and avoids potential security issues.
In our case
0c45773b623bea8c8e75f6c82b208c3cf94ea4f9
is the sha1 forv4.0.2
which, if I'm not mistaken, should not fail the build as it is recent enough. But this failed the build.The text was updated successfully, but these errors were encountered: