ci: release tag workflow #3036
Merged
ci: release tag workflow #3036
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
This adds a new workflow for building and releasing _tagged versions_ of Ghostty. The workflow is triggered automatically by new tags in the format of `vX.Y.Z` but can also be manually triggered by running the workflow from the GitHub Actions UI. Release artifacts are uploaded to a completely separate R2 bucket with its own access policy, retention, API keys, and so on. There is currently no way to switch between "channels" in the macOS app. I will follow up with a separate commit to add this feature.
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.
This adds a new workflow for building and releasing tagged versions of Ghostty. The workflow is triggered automatically by new tags in the format of
vX.Y.Zbut can also be manually triggered by running the workflow from the GitHub Actions UI.Release artifacts are uploaded to a completely separate R2 bucket with its own access policy, retention, API keys, and so on.
There is currently no way to switch between "channels" in the macOS app. I will follow up with a separate commit to add this feature.