{{ message }}
Repository navigation
docs(changelog): reconstruct 6.7.1–6.12.0 from the tag history - #4898
Merged
Merged
Conversation
The v6.12.0 release notes carry the cmd/defaults breaking change, but the CHANGELOG — the stated source of truth — had no section for it or for the agent double-send fix that shipped alongside. Add a [6.12.0] section with both, the BREAKING entry first with the one-line migration.
Contributor
There was a problem hiding this comment.
Pull request overview
Adds the v6.12.0 changelog section documenting the cmd/defaults breaking change and agent duplicate-send fix.
Changes:
- Documents migration guidance and dependency reduction.
- Records the agent message-duplication fix.
- Minor nit: restore the standard
---section separator.
Suppressed comments (1)
CHANGELOG.md:50
- This entry overstates the affected provider set: the built-in Groq, Mistral, and Together adapters build requests from only
SystemPromptandPromptand ignorereq.Messages(for example,ai/groq/groq.go:77-84), so those models did not replay the current turn or charge duplicate history tokens. Please qualify this as applying to providers that serializeMessages, or describe it as a duplicate in the agent request rather than saying every provider/model saw it twice.
- **Current message no longer sent to the provider twice** — every `Ask`/`Stream` sent the turn being answered both as the trailing `Messages` entry and as `Prompt`, and providers replay both, so the model saw each user message twice and every turn paid input tokens for the repeat. `Messages` now carries history only (`Prompt` carries the turn): the Ask path trims the just-recorded duplicate, the streaming path no longer appends it, and the conformance tests pin the inverse guard. Reported by a downstream user with a reproducer. (`agent/`)
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Comment on lines
50
to
52
The changelog had drifted: versioned sections stopped at 6.7.0 while tags ran to v6.12.0, with five releases of material piled under [Unreleased]. Reconstruct the missing sections by walking each tag range and verifying every entry against the code at that tag: - 6.7.1: Gemini streaming, retry jitter, micro agent resume-input, remote chat streaming (all verified absent at v6.7.0, present at v6.7.1). - 6.8.0: AP2 inbound verification, flow HITL, K8s reconcile core, Local fast-path, gRPC-reflection MCP, x402 buyer example/spend observability, A2A conformance, MCP stdio/ws JSON results, x402 spend-cap + A2A SSRF hardening. - 6.9.0: auth-follows-the-socket (default credential removed), micro server -> micro gateway consolidation, micro run scoped as a dev tool, website migration hardening, CVE dep bumps, retraction tooling. - 6.10.0 and 6.11.0: gateway endpoint parsing, AtlasCloud markers, resolver decoupling + HTTP SSE, gRPC reflection option, Redis v9, retraction fixes. - 6.12.0: gains the reasoning controls, MiniMax multimodal history, and README front-door entries alongside the cmd/defaults BREAKING change and the agent double-send fix. Two stale [Unreleased] entries were dropped rather than moved: "Compacted memory summaries" and "Provider failure inspection metadata" describe features already present at v6.6.0, so they were never unreleased. [Unreleased] is now empty with a note that it rolls on each release.
asim
changed the title
This was referenced Aug 30, 2026
asim
added a commit
that referenced
this pull request
Aug 30, 2026
* ci(release): roll CHANGELOG [Unreleased] into the version on tag The changelog once drifted five releases behind the tags, with everything piled under [Unreleased] (reconstructed in #4898), because releases are cut automatically but the rollup was manual. Mechanize it: when the release workflow cuts vX.Y.Z and [Unreleased] has entries, it rewrites the header into an empty [Unreleased] plus a dated [X.Y.Z] section carrying those entries, commits, pushes to master with the release PAT, and tags the rolled commit. If the push is rejected (branch protection), it warns and tags the current HEAD — a release is never blocked on the docs commit. With no entries there is nothing to roll and the step is skipped. * Potential fix for pull request finding Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --------- Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.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
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.
Why
The CHANGELOG — the project's stated source of truth — had drifted five releases behind: versioned sections stopped at 6.7.0 while tags ran to v6.12.0, with everything piled under
[Unreleased](including entries for features that shipped as far back as v6.6.0).What
Full reconstruction of
[6.7.1]through[6.12.0], built by walking each tag's commit range and verifying every entry against the code at that tag (git grepat tag boundaries — commit-title matching alone was unreliable because a 967-file history squash bottoms outgit log -S):cmd/defaultsplugin split (with migration line), agent double-send fix, reasoning controls, MiniMax multimodal history, README front doormicro server→micro gateway,micro runscoped as dev tool, website hardening, CVE bumpsmicro agent resume-input, remote chat streaming (all verified absent at v6.7.0, present at v6.7.1)Two stale
[Unreleased]entries were dropped rather than moved — "Compacted memory summaries" and "Provider failure inspection metadata" describe features already present at v6.6.0, so they were never unreleased.[Unreleased]is now empty with a note that it rolls on each release.Suggested follow-up (not in this PR)
A loop rule that rolls
[Unreleased]into a version section at every tag, so this drift can't recur.🤖 Generated with Claude Code