loop: have DevRel maintain CHANGELOG.md and draft a changelog blog post#3584
Merged
Conversation
The DevRel pass now keeps the changelog living instead of letting it drift: each daily run reconciles a Keep-a-Changelog `[Unreleased]` section against the PRs that actually merged (user-facing entries only; internal loop/CI churn skipped) and rolls it into a dated version heading whenever loop-release cuts a new v6.MINOR.PATCH tag. When enough user-facing work has accumulated (roughly a week's worth, not a near-empty post every day) it also drafts a "what's new" changelog blog post narrating what shipped. Autonomy boundary preserved: CHANGELOG.md upkeep is a safe factual change and rides the auto-merged DevRel PR; the changelog blog post is opened as its own PR but left for the human to review/merge, since blog voice stays with the human. Also fix the CHANGELOG preamble: it claimed calendar versions (YYYY.MM) while tags are semver (v6.MINOR.PATCH). Correct it, add an `[Unreleased]` section seeded from real recent work, and note the historical 2026.0x headings. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CmdEY7pYmV5zzwCjNJ4ykL
Closed
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.
What
Makes the daily DevRel loop keep
CHANGELOG.mdliving and produce a changelog blog post, so the framework's shipped history stays current instead of drifting.DevRel loop (
loop-devrel.yml)The daily coherence pass now does two more things:
## [Unreleased]section against the PRs that actually merged to master — user-facing entries only, internal loop/CI/priorities churn skipped — and rolls[Unreleased]into a dated## [MINOR.PATCH]heading wheneverloop-releasecuts a newv6.*tag. This is a safe factual change, so it rides the existing auto-merged DevRel PR.blog/N.md+ index entry, and opens it as a separate PR left for the human to merge. Blog voice stays with the human, consistent with the existing autonomy boundary.CHANGELOG.md fixes
The preamble claimed calendar versions (
YYYY.MM) while every tag is semver (v6.MINOR.PATCH), and the newest entry was[6.0.0]with 40+ merges since. Corrected the preamble to semver, seeded a real## [Unreleased]section from actual recent work (retrieval memory, scheduled flows, flow grader loop, A2A streaming/continuity, tool-call resilience, first-agent docs, Discord), and marked the old2026.0xheadings as historical.Docs
Updated
internal/docs/CONTINUOUS_IMPROVEMENT.md(pipeline table + DevRel overseer section) to describe the new CHANGELOG/blog responsibilities and reaffirm the autonomy boundary.Why
The changelog had gone stale and was factually wrong about its own versioning scheme. Tying its upkeep to the DevRel loop — which already audits the public surface daily — keeps it accurate automatically, and gives releases a human-readable narrative without adding a human chore.
Notes
loop-devrel.ymlYAML validated.[Unreleased]section is live now.🤖 Generated with Claude Code
Generated by Claude Code