Fix update runners scheduled workflow to check for container-hooks upgrades #2576
Conversation
This file contains 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
Link-
requested review from
mumoshu,
toast-gear,
a team and
nikola-jokic
as code owners
nikola-jokic
approved these changes
May 11, 2023
rentziass
approved these changes
May 12, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Context
Related: #2551
At the moment the update-runners.yaml workflow runs daily to check for new actions/runner releases, but it doesn't do the same for actions/runner-container-hooks.
This PR is to fix the workflow so that it checks for both and creates a PR whenever either of the products is upgraded.