Repository navigation
feat(ci): add a pre-release workflow - #7
Merged
Merged
Conversation
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.
This pull request introduces a new workflow for handling pre-releases and updates the existing release workflow to ensure that only one workflow runs per tag push. The main goal is to prevent pre-release tags from triggering the stable release workflow, which would otherwise publish a full release and update the Homebrew tap incorrectly. The changes are thoroughly documented and include operational improvements and clarifications in the project documentation.
Pre-release workflow addition and release workflow update:
Workflow and release process separation:
.github/workflows/pre-release.ymlthat is triggered by pushing tags containing a hyphen (e.g.,v0.2.0-rc.1). This workflow builds, tests, and publishes a marked pre-release, but never updates the Homebrew tap or serves as the latest release, ensuring pre-releases are isolated from stable user updates..github/workflows/release.ymlto only trigger on stable tags (e.g.,v0.2.0) by excluding tags with a hyphen usingtags: ["v*", "!v*-*"], so pre-release tags do not start the stable release workflow or update the tap. [1] [2]Documentation and operational improvements:
AGENTS.md, including details on version verification, asset packaging, and checksum publication. The documentation also explains why the Homebrew tap is never updated for pre-releases and how the workflow separation is enforced.These changes ensure a clear separation between stable releases and pre-releases, preventing accidental promotion of pre-release builds to end-users and maintaining the integrity of the Homebrew tap.