Prepare v1.4.0 release and changelog guard - #32
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
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 changed
CHANGELOG.mdwith thev1.4.0release notes and historyWhy
Release notes previously existed only in generated GitHub releases, and the
release process did not ensure that a versioned changelog entry was committed
with the tag.
Impact
Future agent-driven releases update the changelog automatically as part of the
request. Manual release dispatches fail before publication if the requested
version is absent from
CHANGELOG.md.Validation
go test -count=1 -race ./...go vet ./...goreleaser checkgoreleaser build --snapshot --cleanE2E_SCOPE=release bash scripts/e2e-init-update.shagainst the snapshot binaryshellcheck scripts/check-release-changelog.shgit diff --check