Automate releases #184
Merged
Automate releases #184
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
There's no need to release darwin builds for the for a kubernetes controller
Because draft releases don't have stable URLs, we create the release notes in one shot with goreleaser.
triarius
force-pushed
the
pdp-812-automate-release-of-agent-stack-k8s
branch
from
8df72ea to
1cf28a8
Compare
triarius
force-pushed
the
pdp-812-automate-release-of-agent-stack-k8s
branch
from
1cf28a8 to
04942c4
Compare
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.
The new step will run on buildkite tag builds and create a draft release on GitHub.
It uses goreleaser, ghch, and github cli. A human will then be able to edit the draft and publish the release.
There was a flaw in the previous release process that meant the controller and container images reported their versions to be different from the release. This was because when the images were built, the tag had not yet been created. The new processes fixes this by creating the release from the tag build rather than creating the tag from the release.