Skip to content
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

Update lifecycle from v0.17.0 to v0.17.1 #389

Merged
merged 1 commit into from
Sep 25, 2023
Merged

Conversation

@edmorley edmorley self-assigned this Sep 25, 2023
@edmorley edmorley marked this pull request as ready for review September 25, 2023 16:01
@edmorley edmorley requested a review from a team as a code owner September 25, 2023 16:01
@edmorley edmorley enabled auto-merge (squash) September 25, 2023 16:01
@edmorley edmorley merged commit 92a10bf into main Sep 25, 2023
35 checks passed
@edmorley edmorley deleted the edmorley/update-lifecycle branch September 25, 2023 19:13
edmorley added a commit that referenced this pull request Oct 19, 2023
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: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.

GUS-W-14329446.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants