ci: add release workflow, align with phoenix-static#11
Merged
Conversation
Add the conventional-commit Release workflow used by the phoenix-static buildpack: on every merge to main it computes the next semver tag from commit subjects/bodies (feat -> minor, fix -> patch, BREAKING -> major) and cuts a GitHub Release. Uses only first-party tooling (git, gh, actions/checkout). Also bump CI's checkout action v3 -> v6 to match.
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.
What
Brings this buildpack's release process in line with the phoenix-static
buildpack:
.github/workflows/release.yml— an automated, conventional-commitdriven Release workflow (identical to the one in
gigalixir-buildpack-phoenix-static).ci.yml'sactions/checkoutfromv3tov6to match.Why
The Elixir buildpack had no automated release/versioning. This adds the same
hands-off flow phoenix-static already uses, so merges to
mainproduce taggedGitHub Releases without manual steps.
How it works
On every push to
main, the workflow computes the next semver tag from theconventional-commit messages since the last
v*tag:feat:→ minorfix:→ patchBREAKING CHANGE/!:→ majordocs/chore/refactor/test/ci) → no tag, no releaseIt then creates the tag and a GitHub Release with auto-generated notes. Only
first-party tooling is used (git, the preinstalled
ghCLI, andactions/checkout); no third-party actions. Aconcurrencygroup preventsoverlapping releases, and an idempotency guard skips tags that already exist.
Baseline / rollout notes
v2.11.0(currentmaintip), so the next releasablemerge will produce
v2.12.0.ci:-typed, so once merged the workflow runs andcorrectly produces no release.
mainwhen the next
feat:/fix:lands.Deployment
No
root/-style deployment needed — this only affects CI/release automationin the repo.