Conversation
Collaborator
|
Honestly, I don't know how to think about this one. This is not a bad idea but the keeping it up to date is kind of a hell. Normally, we only need to secure the release pipeline. Using hash is almost the same as using the exact semver (v0.1.2 for example). It's also useful to use hash when a fix is here but yet release. We should dive deeper for the pros and cons of this changes, I don't think it's a bad idea but we need more insight from other point of view for this one. |
frack113
force-pushed
the
yaml
branch
3 times, most recently
from
d7387b4 to
d7b5bd2
Compare
frack113
changed the title
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
2 participants
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
Update GitHub Actions to latest versions across all CI/CD workflows.
Changes