chore(ci): convert to a push-button release workflow #725
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
Currently, the release workflow requires someone to manually inspect the changes since the last release, decide on a good version number to use, create that tag locally, and push it to GitHub to trigger a release. Instead, we could follow the pattern established with our generated SDKs and use Conventional Commit tags to enable automatic calculation of the next version number. This enables us to release with a single click, which makes it easier to release quickly and share responsibility for creating releases.
displague
approved these changes
Jul 10, 2024
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.
Currently, the release workflow requires someone to manually inspect the changes since the last release, decide on a good version number to use, create that tag locally, and push it to GitHub to trigger a release.
Instead, this follows the pattern established with our generated SDKs, which use Conventional Commits tags to automatically determine the next release version and construct the release notes for the GitHub release.
The updated push-button workflow creates the correct release automatically and then runs the pre-existing goreleaser action to attach the terraform provider builds to the existing GitHub release.