Add automation for updating builder lifecycle version #404
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
Previously we had to manually keep track of upstream lifecycle releases, and then open PRs to update the builder manifest for each builder with the new version. Now, every Monday at 6am UTC, a GitHub Actions job will check for updates, and open a PR if the latest lifecycle version is newer than that used by the `heroku/builder:22` builder. (This means lifecycle version pinning will be supported too for eg our legacy images, since only builder images on the latest version will end up being updated each time.) This new workflow can also be triggered manually thanks to the `workflow_dispatch` annotation.
|
This is super neat! :) Thanks for adding this one! 🎉 |
Malax
approved these changes
Oct 19, 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.
Previously we had to manually keep track of upstream lifecycle releases, and then open PRs to update the builder manifest for each builder with the new version.
For example:
#389
Now, every Monday at 8am UTC, a GitHub Actions job will check for updates, and open a PR if the latest lifecycle version is newer than that used by the
heroku/builder:22builder. (This means lifecycle version pinning will be supported too for eg our legacy images, since only builder images on the latest version will end up being updated each time.)This new workflow can also be triggered manually thanks to the
workflow_dispatchannotation.GUS-W-14329446.