ci: migrate release process from GitHub Actions to Buildkite with Chinmina#136
Open
jamestelfer wants to merge 5 commits intomainfrom
Open
ci: migrate release process from GitHub Actions to Buildkite with Chinmina#136jamestelfer wants to merge 5 commits intomainfrom
jamestelfer wants to merge 5 commits intomainfrom
Conversation
jamestelfer
force-pushed
the
migrate-release-to-buildkite-chinmina
branch
from
6e28768 to
0061686
Compare
In preparation for a full migration of the release process to Buildkite.
jamestelfer
force-pushed
the
migrate-release-to-buildkite-chinmina
branch
3 times, most recently
from
393d86b to
8f943af
Compare
Replace the hybrid Buildkite/GitHub Actions release workflow with a Buildkite-only pipeline using Chinmina for ephemeral GitHub authentication. The release process is entirely in Buildkite, and no longer requires GitHub personal access tokens.
jamestelfer
force-pushed
the
migrate-release-to-buildkite-chinmina
branch
3 times, most recently
from
531360b to
2b2db5b
Compare
Add release section to goreleaser config to ensure changelog is properly published to GitHub releases with appropriate header and footer formatting.
- Change snapshot.name_template to snapshot.version_template - Change archives.format to archives.formats - Rename brews to homebrew_casks (removes custom test and install scripts as casks use a different structure) These changes address all deprecation warnings from GoReleaser v2.
jamestelfer
force-pushed
the
migrate-release-to-buildkite-chinmina
branch
from
2b2db5b to
06d314b
Compare
jamestelfer
changed the title
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.
Purpose
Simplify and consolidate the cfparams release process by removing the dependency on GitHub Actions and AWS Secrets Manager. The current hybrid approach requires Buildkite to trigger GitHub Actions, which then performs the actual release work. This is complicated and relies on long-lived credentials stored in AWS Secrets Manager.
Going for a Buildkite-only pipeline with Chinmina for ephemeral GitHub authentication makes the release process more straightforward.
Notably:
git-cliffworks better for pre-release versions than our previous strategy, and gets rid of a Node dependency.Context
pipeline:binary-releasefor releases/tags andorg:homebrew-tap-publishfor homebrew tap updates