Merged
Conversation
62821e4 to
bdbdb63
Compare
Member
|
Is there a way to have the CLI binaries attached to the GitHub release? |
Member
Author
Not directly through CRT (at least not currently), we'd have to build our own workflow to do that. I'm not sure it's worth uploading it there though, for a couple of reasons:
|
bdbdb63 to
37412a0
Compare
37412a0 to
eaaee64
Compare
eaaee64 to
6824fe2
Compare
kmoe
approved these changes
Dec 6, 2023
This file contains hidden or 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
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.
Context
Releasing currently requires a number of additional steps outside of GitHub. For a simple project with simple release pipeline such as this one, there is no strong benefit to do multi-staged releasing, as some other bigger projects do.
Proposal
Simplify release process by moving promotion steps into a GHA workflow.
TODO
proj-terraform-exec-bottobobrepoBOB_GITHUB_TOKEN