Skip to content

release: v0.7.0 — promote CHANGELOG + release artifacts#57

Merged
jcsvwinston merged 1 commit into
mainfrom
release/v0.7.0-prep
May 14, 2026
Merged

release: v0.7.0 — promote CHANGELOG + release artifacts#57
jcsvwinston merged 1 commit into
mainfrom
release/v0.7.0-prep

Conversation

@jcsvwinston
Copy link
Copy Markdown
Owner

Summary

Resolves the /release-prep blockers found after the v0.7.0 tag was cut on fce7c57. The tag currently points at fce7c57 (pre-release-commit); once this merges it must move to the merge commit — see Tag move below.

This PR makes v0.7.0 release-ready. No code changes — docs, CHANGELOG, and release artifacts only.

What's in here

  • CHANGELOG[Unreleased] promoted to [0.7.0] - 2026-05-14; fresh empty [Unreleased] added; section ordering fixed to newest-first (Keep-a-Changelog); missing [0.7.0]/[0.6.0]/[0.5.5] compare links added. The v0.7.0 section opens with a Compatibility statement (both pre-v1.0 breaking changes — SendGrid removal, Casbin default-deny — with DEP/MA citations) and closes with a Dependencies subsection.
  • docs/templates/ — adds deprecation_notice.md and migration_assistant.md, the canonical scaffolds that DEPRECATION_TEMPLATE.md / MIGRATION_ASSISTANT_CONVENTIONS.md reference but were never committed. This was the stable-contract-docs gate failure.
  • docs/reports/ — commits the v0.7.0 release artifacts: compatibility_harness_latest.md (3/3 READY), compatibility_report_2026-05-14.md (8/8 READY), dependency_impact_2026-05-14.md, dependency_critical_review_2026-05-14.md, and mssql_oracle_stability_2026-05-14.md (the 10/10 + 10/10 post-sprint drill).
  • mssql_oracle_stability_report.md — post-ADR-004-sprint drill section flipped from "queued" to "completed" with the 100%/100% result.

Critical dependency review (recorded)

Two critical-set deps moved since v0.6.0, both reviewed and ACCEPTED (full rationale in docs/reports/dependency_critical_review_2026-05-14.md):

  • go-mssqldb v1.8.2 → v1.10.0 — additive-only, govulncheck-clean, blank driver import only, 10/10 drill passed with it in the tree.
  • otlptracehttp v1.35.0 → v1.43.0 — no breaking changes, no CVEs, encapsulated in pkg/observe, firewall clean.

Release-prep verdict

Gate Result
contract freeze PASS
compatibility harness PASS (3/3, READY)
dependency impact reviewed + accepted
compatibility report READY (8/8)
governance (release mode) PASS
docs & changelog PASS
go test ./... PASS (0 failures)

Tag move (post-merge)

The v0.7.0 git tag currently points at fce7c57. After this PR merges, the tag must be deleted and recreated on the merge commit so it reflects a release-ready state. The repo owner approved this move on 2026-05-14.

Test plan

  • bash scripts/ci/check_contract_freeze.sh — 6/6 PASS
  • bash scripts/ci/run_compatibility_harness.sh --enforce-threshold — 3/3, READY
  • bash scripts/release/generate_compatibility_report.sh --enforce-threshold — 8/8, READY
  • go test ./... — clean
  • governance-checker (release-prep strict mode) — PASS

🤖 Generated with Claude Code

Resolves the /release-prep blockers found after the v0.7.0 tag was cut
on fce7c57:

- CHANGELOG: promote [Unreleased] → [0.7.0] - 2026-05-14, add a fresh
  empty [Unreleased], fix section ordering (newest-first per
  Keep-a-Changelog), and add the [0.7.0]/[0.6.0]/[0.5.5] compare links
  that were missing. New v0.7.0 section opens with a Compatibility
  statement (both pre-v1.0 breaking changes with DEP/MA citations) and
  closes with a Dependencies subsection recording the critical-dep
  review.

- docs/templates/: add deprecation_notice.md and migration_assistant.md
  — the canonical scaffolds that DEPRECATION_TEMPLATE.md and
  MIGRATION_ASSISTANT_CONVENTIONS.md already reference but were never
  committed. This was the stable-contract-docs gate failure in the
  compatibility report.

- docs/reports/: commit the v0.7.0 release artifacts —
  compatibility_harness_latest.md (3/3 READY),
  compatibility_report_2026-05-14.md (8/8 READY),
  dependency_impact_2026-05-14.md,
  dependency_critical_review_2026-05-14.md (go-mssqldb v1.8.2→v1.10.0
  and otlptracehttp v1.35.0→v1.43.0 reviewed and ACCEPTED), and
  mssql_oracle_stability_2026-05-14.md (the 10/10+10/10 post-sprint
  drill on main).

- mssql_oracle_stability_report.md: flip the post-ADR-004-sprint drill
  section from "queued" to "completed" with the 100%/100% result.

Release-prep verdict after this commit: contract freeze PASS,
compatibility harness PASS, dependency impact reviewed, compatibility
report READY, governance PASS, docs & changelog PASS, go test ./...
PASS.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@jcsvwinston jcsvwinston merged commit ed5689b into main May 14, 2026
9 checks passed
jcsvwinston added a commit that referenced this pull request May 14, 2026
Session End Protocol for the iteration that swept the post-ADR-004
queue, released v0.7.0, and landed the ES256 + AWS Secrets Manager MVP
(PRs #56, #57, #58).

- Archive the iteration at docs/iterations/2026-05-14-v0.7.0-release-and-es256.md.
- Reset CURRENT_ITERATION.md to an empty slate with a ranked
  candidate-next-steps list (CSRF hardening is the top item).
- Refresh HANDOFF.md: main @ e53f72b, v0.7.0 tagged, no active
  iteration, open housekeeping noted.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@jcsvwinston jcsvwinston deleted the release/v0.7.0-prep branch May 15, 2026 16:42
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