fix(ci): add release build and GitHub release steps back to main pipeline - #80
Merged
Merged
Conversation
…line PR #79 split the pipeline into validation-only (pipeline.yml) and a separate release pipeline (pipeline.release.yml), but the release pipeline was never wired in Buildkite. Merging to main created a tag but no binary or GitHub release. Fix: restore release_build (binary + sha256) and GitHub release steps after the tag step in pipeline.yml, so a single run produces both the tag and the release. The release pipeline remains available as a standalone option for manually pushed tags. Also merges build+checksum into one step in pipeline.release.yml to match the same-agent optimization done in pipeline.yml.
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
1 participant
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.
Problem: PR #79 split the pipeline into validation-only (
pipeline.yml) and a separate release pipeline (pipeline.release.yml), but the release pipeline was never wired as a separate Buildkite pipeline. Merging to main created a tag but no binary or GitHub release.Fix: Restores
release_build(binary + sha256) andrelease(GitHub Release) steps after thetagstep inpipeline.yml, so a single pipeline run on main produces both the tag and the release.Also includes: Merges build+checksum into one step in
pipeline.release.yml(same-agent optimization from the previous PR that was left uncommitted).Release pipeline is still available as a standalone option if a separate Buildkite pipeline is configured for tag-push triggers.