chore: prepare CHANGELOG for v3.9.3 release - #191
Merged
Merged
Conversation
Adds the [3.9.3] section for the 22 grouped dependency bumps in #190. Also backfills the missing [3.9.2] section: v3.9.2 was tagged and published on 2026-08-28 without a CHANGELOG entry. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Summary
Prepares the CHANGELOG for a v3.9.3 patch release. Patch is the right bump: the only commit since
v3.9.2is a Dependabot group update touchinggo.mod/go.sumonly, with no API or behavior change.Release content
godirective stays on 1.26.7.Also: backfills the missing v3.9.2 section
v3.9.2was tagged and published on 2026-08-28 but never got a CHANGELOG entry, so its contents (#187 dependency bumps, #188 codeql-action 3 → 4) were invisible in the changelog. That section is now filled in from the tag range, with a short note recording the backfill.Two process notes for that release, neither fixed here since the tag is already published:
v3.9.2is a lightweight tag, whilev3.9.0andv3.9.1are annotated. The release workflow reads the tag message, so annotated is the intended form.v3.9.3will be tagged annotated, per the documented flow.Verification
dc50d53, the chore(deps): bump the go-minor-patch group across 1 directory with 22 updates #190 merge commit: CI, golangci-lint, Security, Fuzzing.go mod verify,go build ./...andgo vet ./...all clean. The only test failures were testcontainer tests that require Docker, which was not running on that machine; CI ran those same tests with Docker and passed.🤖 Generated with Claude Code