docs(changelog): reconcile release history and prepare 0.11.0#237
Merged
Conversation
Back-fill the 0.9.1, 0.9.2, and 0.10.0 sections that were released via GoReleaser but never recorded in CHANGELOG.md, and move already-shipped work out of [Unreleased]: replay mode (#209, 0.10.0), PRODUCER span kind (#214, 0.9.2), and reader-based replay entry points (#216, 0.9.2). Promote the genuinely-unreleased work to [0.11.0]: the INTERNAL span-kind change (#213/#231), the public pkg/synth trace-generation API (#199/#234), and the sampling trace-integrity invariants (#74/#235/#236), plus the OTLP exporter dependency bumps (#228, #229). Note that 0.9.2 was tagged after 0.10.0 from a later commit, so the next minor release is 0.11.0, and fix the compare links. Co-Authored-By: Claude Opus 4.8 <[email protected]> Claude-Session: https://claude.ai/code/session_01G1HxLtj1Uu2Y3K6Ea5P9zR
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.
Summary
Prepares the changelog for a v0.11.0 release and reconciles the hand-maintained
CHANGELOG.mdwith the releases that GoReleaser actually cut.The changelog had drifted: it only documented releases through 0.9.0, while GoReleaser tagged 0.9.1, 0.9.2, and 0.10.0 (with release notes auto-generated from raw commit messages). Meanwhile
[Unreleased]listed work that had already shipped in those tags.What changed
[0.9.1],[0.9.2], and[0.10.0]sections from their tagged commits.[Unreleased]:import --record(Trace import loses per-request fidelity; explore a replay/recording mode #209) → shipped in 0.10.0producer: truePRODUCER span kind (Support PRODUCER span kind for async producers #214/Support PRODUCER span kind for async producers #230) → shipped in 0.9.2[0.11.0]:INTERNALspan kind for same-service sync calls (Emit INTERNAL span kind for in-process (same-service) calls #213/feat: emit INTERNAL span kind for same-service sync calls #231) — behavior changepkg/synthtrace-generation API (Expose a public trace-generation API in pkg/synth for pipeline testing #199/feat: expose public trace-generation API in pkg/synth (#199) #234)[Unreleased]link.Note on version ordering
v0.9.2was tagged (Jul 2) afterv0.10.0(Jun 17), from a later commit, so its version number is out of sequence with its release date. A short note in the 0.9.2 entry records this, and the next minor release is 0.11.0 (not a 0.10.x line), since GoReleaser derives the next version from the highest existing semver tag (v0.10.0).Release
Tagging
v0.11.0triggers the GoReleaser workflow (GitHub release + Homebrew tap). Per the agreed plan, the tag will be pushed after this PR merges so the release is cut frommain.Verification
go build ./...— cleango test ./...— all packages pass🤖 Generated with Claude Code
Generated by Claude Code