-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Pin GitHub actions workflows to a version #9435
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pin GitHub actions workflows to a version #9435
Conversation
Pinning has a few benefits: - Workflows are more repeatable for a given a commit ID. We know exactly what steps were performed. - Updating the workflows version goes though the PR validation process, so we know whether we want to apply a change to the entire repository. - We avoid potential issues with breaking changes in the upstream workflows.
|
@swift-ci test |
|
Let's hold off. We will need a new tag to fix the Android workflows. |
|
Never mind, we are not using android testing yet. |
jakepetroules
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LG but please make sure to do the same thing for swift-build.
Also hoping we get swiftlang/github-workflows#198 landed soon.
The Swift-build change already landed :) |
|
Although I am usually against merging changes where builds fails. @MaxDesiatov force merged the PR as this only modifies GitHub Actions, and there were Jenkins jobs failure, which is unrelated to this change. Thanks for force merging, @MaxDesiatov |
Pinning has a few benefits: