Repository navigation
chore(release): 3.6.0 - #715
Merged
Merged
Conversation
Minor release: service-contract graph (OpenAPI, protobuf, and GraphQL schemas read into the call graph, handlers and generated clients bound to their operations, contract changes graded against real consumers including sibling repositories), agent-loop receipts and session ledger, cross-worktree coordination, new verifiable claim kinds, and infrastructure-to-code binding. The new capabilities ship behind opt-in presets; the default surface is unchanged. Index schema version is now 17 (one-time background reindex on upgrade). No breaking changes. See CHANGELOG.md for the full notes. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Rewrite the promoted [3.6.0] section into the concise, grouped, PR-referenced form of prior releases (e.g. 3.5.0): a tagline, themed highlights, breaking/ behavior changes, and a fixed list. Fixes an internal contradiction in the accumulated notes (schema version stated as both 16 and 17 — it is 17) and removes a stray mid-section tagline. The Release workflow lifts this section verbatim as the GitHub Release notes. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.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.
Status
Release PR for v3.6.0 — full release of current
main, nothing cherry-picked (per request).What it does
Standard
chore(release)bump following the v3.5.0 (#617) pattern:package.json+package-lock.json→ 3.6.0CHANGELOG.md: a fresh empty## [Unreleased], and the accumulated notes promoted to## [3.6.0] - 2026-11-09with a tagline and a closing preset/schema note. The Release workflow extracts this section verbatim as the GitHub Release notes.3.6.0-default.jsonconfig compatibility fixture + README entry (config behavior is unchanged this release; the frozen-fixture test requires a fixture matching the new package version).What ships
The window since v3.5.0: the service-contract graph (OpenAPI / protobuf / GraphQL read into the graph, handler + generated-client binding, consumer census across sibling repos, contract-change grading), agent-loop receipts + session ledger, cross-worktree coordination, new
verify_claimkinds, IaC-to-code binding, onboarding/background self-healing, and the usual fixes. All additive behind existing/opt-in presets; the default tool surface is unchanged. Index schema version is now 17 (one-time background reindex on upgrade). No breaking changes.Proof
config-manager.test.ts42/42 (new 3.6.0 fixture round-trips unchanged).doc-claim-sync.test.ts15/15.tsc --noEmitclean.How to release
Merge this PR, then push the
v3.6.0tag at the merge commit — that triggers the Release workflow, which creates the GitHub Release (from the CHANGELOG section) and publishes to npm via Trusted Publishing (OIDC). The workflow's "reachable from main" guard is satisfied because the tag lands onmain.🤖 Generated with Claude Code