Repository navigation
Conversation
… footer Set START_COMMIT to the last commit covered by CHANGELOG-legacy.md and override the git-cliff footer to point to it.
Contributor
|
We can change to v8.0.0, as a new main version. |
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.
Summary
Switch go-api to tag-based releases.
developbuilds day to day, and each release tag is deployed there first for testingvX.Y.Zversions — the same chart tested on stagingdevelopwork stays outChanges
masterand temporaryfeature/banjo-stackpublish triggersCHANGELOG.mdtoCHANGELOG-legacy.mdSTART_COMMITset to the last commit covered by the legacy changelog (86b9ddd3), so the generated changelog continues where it stopsCHANGELOG-legacy.mdv0.3.1to fixrelease.shexiting with 141 (SIGPIPE) on repos with many tags (fix(release): avoid SIGPIPE when listing tags under pipefail toggle-corp/fugit#4)docs/release.md(release, hotfix, rollback); README links to itWhat a
vX.Y.Ztag publishesghcr.io/ifrcgo/go-api:vX.Y.Z.c<sha7>oci://ghcr.io/ifrcgo/ifrcgo-helm:X.Y.Z-<sha7>vX.Y.Z, with the generated changelog and the chart version to deployHeads-up for contributors
The changelog is generated from commit messages. Every commit needs a Conventional Commit prefix (
feat:,fix:,chore:…), otherwise it's left out of the changelog. Merge commits are ignored.Before the first release
v0.3.1)v7.0.0tag exists ->v7.1.0orv8.0.0)targetRevisionto the first release.Follow-up
Testing
release.shin a throwaway clone (nothing pushed): the changelog contains only commg, and the footer link is correct.Fix broken /docs) and merge commits don't appear in the generated changelog.