Skip to content

chore(release): v0.6.0 — Observability & Decorators (M6.4)#50

Merged
danielPoloWork merged 1 commit into
masterfrom
chore/release-v0.6.0
Jun 14, 2026
Merged

chore(release): v0.6.0 — Observability & Decorators (M6.4)#50
danielPoloWork merged 1 commit into
masterfrom
chore/release-v0.6.0

Conversation

@danielPoloWork

Copy link
Copy Markdown
Owner

Summary

Close Milestone 6 → v0.6.0 — Observability & Decorators. Bump the version, roll the changelog, draft the release notes, and refresh the README and roadmap. No code behaviour changes — this is the milestone-closing release PR (ADR-0004 §2).

Motivation

ROADMAP §6.4 — the release item that seals Milestone 6 (the InstrumentedPool Decorator, the PoolObserver, and the zero-overhead verification landed in PRs #47#49). Versioning and the agent-prepares / human-tags-and-publishes boundary follow ADR-0004 §2 and ADR-0008.

Changes

  • version.hppMINOR=6 PATCH=0, PBR_MEMORY_POOL_VERSION_STRING = "0.6.0"; the pool_smoke version-check TEST_CASE asserts the new components.
  • CHANGELOG.md — the Unreleased block (M6.1 Decorator, M6.2 Observer, M6.3 zero-overhead test) is rolled into a sealed ## [0.6.0] — 2026-06-14 block with a milestone headline; the footer link references are rewritten ([Unreleased]compare/v0.6.0...HEAD, new [0.6.0]), and a fresh empty Unreleased is seeded.
  • docs/releases/v0.6.0.md — human-prose release notes (Decorator, Observer, the memory_pool_growths accessor, the zero-overhead contract) for release.yml to use as the GitHub Release body.
  • README.md — status badge (v0.5.0 dynamic growthv0.6.0 observability), a new At a glance observability bullet, the status paragraph, and the milestone table (Milestone 6 → ✅ complete, Milestone 7 → ⏳ next).
  • ROADMAP.md — §6.4 flipped to [x] with the inline summary; a new M6 Session Checkpoint entry (next session resumes at Milestone 7).

Design Patterns

  • None new — this PR closes the milestone in which Decorator (ADR-0025) and Observer (ADR-0026) were adopted; both are already Implemented in the catalogue. With them, every pattern planned through Milestone 6 is realised.

Verification

  • Builds cleanly (MSVC 19.51 locally; full matrix via CI)
  • Unit tests pass — full suite 10/10; the version-check case asserts 0.6.0
  • markdownlint clean on the edited content (the lone MD060 hit is a pre-existing, unedited repo-layout table flagged only by a newer local markdownlint than CI's pinned version)
  • N/A — docs + version-bump release PR, no library code change

Documentation Impact

Maintainer follow-up (post-merge)

Per ADR-0008: after merging, the agent tags v0.6.0 from master and pushes it; release.yml builds the artifacts and drafts the GitHub Release from docs/releases/v0.6.0.md; the maintainer clicks Publish.

🤖 Generated with Claude Code

Close Milestone 6. Bump version.hpp to 0.6.0 (MINOR 5 → 6) and update the
pool_smoke version-check TEST_CASE in lockstep. Roll the CHANGELOG
Unreleased block (M6.1–M6.3) into a sealed `[0.6.0] — 2026-06-14` block
with a milestone headline, rewrite the bottom-of-file link references, and
seed a fresh empty Unreleased. Add docs/releases/v0.6.0.md release notes
for release.yml to consume as the GitHub Release body.

Refresh README: status badge (v0.5.0 dynamic growth → v0.6.0
observability), a new "At a glance" observability bullet, the status
paragraph, and the milestone table (Milestone 6 → complete, Milestone 7 →
next). Flip ROADMAP §6.4 to [x] with the inline summary and add the M6
session checkpoint (next session resumes at Milestone 7).

No spec row changes — observability is additive instrumentation. The
maintainer reviews and merges this PR, then the agent tags v0.6.0 from
master (ADR-0008) and the maintainer clicks Publish on the draft Release.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@danielPoloWork danielPoloWork marked this pull request as ready for review June 14, 2026 09:14
@danielPoloWork danielPoloWork merged commit 5fe8a11 into master Jun 14, 2026
31 checks passed
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.

1 participant