AsiBackbone 7.2.1 Release Readiness Record
Release date: 2026-10-18
7.2.1 is a backward-compatible patch release for the stable 7.x package
family. It corrects endpoint-governance capability enforcement without adding
public API or changing package dependencies, durable schemas, canonical wire
values, target framework, or binary assembly identity.
This record is a pre-tag checklist. Do not create v7.2.1 or publish packages
until the release-preparation pull request is merged to protected main and
the required hosted checks pass on the release candidate. Check each item when
its evidence exists.
Version and compatibility boundary
- [ ]
Directory.Build.propsresolves package version7.2.1. - [ ]
AssemblyVersionremains7.0.0.0andFileVersionis7.2.1.0. - [ ]
CITATION.cffand.zenodo.jsonreport version7.2.1and release date2026-10-18. - [ ] Template fallback package references use
7.2.1. - [ ] NuGet lock files are refreshed for the
7.2.1in-repository graph. - [ ] Documentation release claims identify
7.2.1as released and current. - [ ] Public API baselines pass with no stable API change.
Compatibility review
- [ ] The only runtime change since
v7.2.0is the endpoint-governance fix that validates required capability grants before acknowledgment, deferral, escalation, or audit completion. - [ ] Package IDs, public namespaces, target framework, package dependencies, durable schemas, canonical wire values, and binary assembly identity are unchanged.
- [ ] Hosts implementing
IEndpointCapabilityGrantValidatorare told that the supplied decision may be acknowledgment-required, deferred, or escalation-recommended and that a valid grant should preserve it. - [ ] Regression tests cover missing and held grants plus fail-open and fail-closed missing-validator behavior.
Local release-candidate validation
- [ ] Version consistency passes for
7.2.1andv7.2.1. - [ ] Documentation release-claim validation passes for
v7.2.1. - [ ] Package lock-file, dependency-suppression, API-baseline, architecture, and documentation-continuity validators pass.
- [ ] Locked restore passes.
- [ ] Debug and Release builds pass with zero warnings and errors.
- [ ] The full local test suite passes; provider tests that require hosted SQL Server or PostgreSQL are covered by the service-container CI job.
- [ ] Formatting verification passes.
- [ ] DocFX completes with zero warnings and errors under
--warningsAsErrors. - [ ] All eleven stable packages pack as
7.2.1and pass package metadata/content validation. - [ ] Template and clean external-consumer smoke tests pass.
Hosted evidence required before tagging
- [ ] CI, stable release validation, CodeQL, dependency review, dependency scanning, provider-contention, template smoke, external-consumer, and documentation link validation jobs are green for the release-candidate commit.
- [ ] The non-publishing package workflow produces the expected package, SBOM, hash, and release-evidence artifacts for maintainer review.
- [ ] The tag will be created from the validated commit already merged to
protected
main, after CI on that merge commit has completed.
Post-publish evidence
- [ ] All eleven packages are visible on NuGet.org at
7.2.1with expected metadata, README content, icons, and repository commit data. - [ ] The GitHub Release contains the required packages, symbols, SBOMs, manifests, hashes, release notes, and provenance evidence.
- [ ] Source Link and GitHub attestation verification pass against the exact published artifacts.
- [ ] The documentation site publishes the
7.2.1release pages and sitemap.
See also: