Skip to content

loop: have DevRel maintain CHANGELOG.md and draft a changelog blog post#3584

Merged
asim merged 1 commit into
masterfrom
claude/loving-meitner-3Etoi
Jul 1, 2026
Merged

loop: have DevRel maintain CHANGELOG.md and draft a changelog blog post#3584
asim merged 1 commit into
masterfrom
claude/loving-meitner-3Etoi

Conversation

@asim

@asim asim commented Jul 1, 2026

Copy link
Copy Markdown
Member

What

Makes the daily DevRel loop keep CHANGELOG.md living 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:

  • CHANGELOG upkeep (auto-merged). Each run reconciles a Keep-a-Changelog ## [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 whenever loop-release cuts a new v6.* tag. This is a safe factual change, so it rides the existing auto-merged DevRel PR.
  • Changelog blog post (drafted, not auto-merged). When enough user-facing work has accumulated (roughly a week's worth — deliberately not a near-empty post every day), it drafts a "What's new in Go Micro" post as the next-numbered 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 old 2026.0x headings 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

  • No code changes; workflow + docs + changelog only. loop-devrel.yml YAML validated.
  • Takes effect on the next DevRel run (07:00 UTC or manual dispatch); the seeded [Unreleased] section is live now.

🤖 Generated with Claude Code


Generated by Claude Code

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
@asim asim merged commit b49f507 into master Jul 1, 2026
10 checks passed
@asim asim mentioned this pull request Jul 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants