docs: move 1.9.0 entry out of Unreleased in CHANGELOG#4
Merged
Conversation
DelineaLaari
force-pushed
the
docs/changelog-v1.9.0
branch
from
2301b3c to
9afc661
Compare
andrespires
approved these changes
May 14, 2026
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
2 participants
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.
Trailing cleanup after the v1.9.0 release was cut. The CHANGELOG entry for the
checksubcommand was still under## [Unreleased]because the release tag was pushed directly (the canonical release notes are on the v1.9.0 release page and in the goreleaser-generated changelog). This PR just moves the entry into a dated## [1.9.0] - 2026-05-14block so the file matches reality.No code changes; CHANGELOG.md only.