-
Notifications
You must be signed in to change notification settings - Fork 39
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
release action: Create new release from list, include old release #40
Conversation
This change updates the release GitHub Actions workflow to build a new release instead of modifying an existing one. The previous "latest" release will be deleted. The release will contain all sysexts listed in "release_build_versions.txt" as well as all sysexts included in the previous latest release. It will generate a Release.md to be included in the release. The change also updates the workflow to only run when the tag "latest" is pushed. Signed-off-by: Thilo Fromm <[email protected]>
(I'm not around for more than a week, feel free to amend and merge this PR as you see fit) |
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.
Thanks, looks good
@@ -2,7 +2,7 @@ name: Build and release Systemd sysext images | |||
on: | |||
push: | |||
tags: | |||
- '*' | |||
- 'latest' |
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.
Improvement: Also release on a weekly cadence
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.
Ah, and should we always release main
? Maybe a new action could run on every push and create a latest
tag and trigger this action here (I think it won't get invoked by another workflow as this is a mechanism to prevent recursion).
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.
Eventually, yes. For this (and the weekly build cadence) to add value we should first make the build auto-detect new versions for all sysexts (like it does for Kubernetes already): I've opened a tracking issue for that: #42
This change updates the release GitHub Actions workflow to build a new release instead of modifying an existing one. The previous "latest" release will be deleted.
The release will contain all sysexts listed in
"release_build_versions.txt" as well as all sysexts included in the previous latest release. It will generate a Release.md to be included in the release.
The change also updates the workflow to only run when the tag "latest" is pushed.