docs(changelog): roll [Unreleased] into [3.3.0] - #79
Merged
Merged
Conversation
Minor rather than patch: go.yml gained two inputs (go-cache, postgres-ready-timeout). Both default to current behaviour, so consumers are unaffected until they opt in, but new inputs are additive API. Pushing the v3.3.0 tag moves the floating v3 tag and publishes the release notes from this section, per release.yml. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Pa92NWDRAbDNXGrSuqcQDa
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.
Release prep for v3.3.0, covering #76, #77 and #78.
Why minor, not patch
go.ymlgained two inputs in #78 —go-cacheandpostgres-ready-timeout. Both default to current behaviour, so every existing consumer is unaffected until it opts in, but new inputs are additive API. They're listed under a new### Addedheading; the rest stays under### Fixed.What happens on the tag
Per
release.yml, pushingv3.3.0moves the floatingv3tag and publishes a GitHub Release using this section as the notes. So this needs to merge before the tag is pushed, or the release publishes with empty notes.Downstream
HordiaLabs/store-postgresis waiting on this — itsCIhas failed on every push tomainsince 2026-06-11 due to the mixed-case image ref fixed in #78. It pins by SHA (no floating@v3), so Dependabot will raise the bump once the tag exists.🤖 Generated with Claude Code
https://claude.ai/code/session_01Pa92NWDRAbDNXGrSuqcQDa