chore(release): cut v1.1.0 (Milestone 11, spec & assurance hardening) - #47
Merged
Conversation
Consolidate Milestone 11 — the seven-PR follow-up to the post-1.0
specification review — into the v1.1.0 release. MINOR under SemVer:
additive (a new opt-in security-fuzzing build surface) with no breaking
change; the 1.0 public API is unchanged and upgrading is drop-in.
- Bump D4NP_UTIL_VERSION_{MINOR,STRING} to 1.1.0 in version.hpp and the
README Status badge (version-lockstep); update the version assertions in
smoke_test.cpp and library_version_test.cpp.
- Roll [Unreleased] into docs/changelog/v1/v1.1.0.md (+ index row) and
reset [Unreleased]; draft release notes at docs/releases/v1.1.0.md
(+ index row).
M11 shipped: error-handling policy ADR-0029, C4 component diagram,
per-component contract table, distribution/ABI policy ADR-0030, security
fuzzing + threat model + non-crypto hash scoping ADR-0031, benchmark
targets, and the FlatMap find/example reconciliation.
Local verify (MSVC): util_tests 221/221 green (incl. the bumped version
assertions); consistency_lint passing (version-lockstep across
version.hpp, README badge, changelog, and release notes).
Per AGENTS §11 the maintainer opens/merges this PR, publishes the GitHub
Release, and closes the M11 milestone.
Co-Authored-By: Claude Opus 4.8 (1M context) <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
1 participant
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.
Summary
Cuts v1.1.0, consolidating Milestone 11 — Specification & Assurance Hardening (the
seven-PR follow-up to the post-1.0 spec review). MINOR under SemVer: additive, no breaking
change; the 1.0 public API is unchanged and upgrading is drop-in.
Motivation
Every acceptance criterion from the specification review is now merged (11.1–11.7). This release
packages that work and closes the M11 milestone. Per AGENTS §11 the agent drafts the release; the
maintainer opens/merges, tags, and publishes.
Changes
1.0.0 → 1.1.0:D4NP_UTIL_VERSION_{MINOR,STRING}inversion.hpp, the READMEStatusbadge, and the version assertions insmoke_test.cpp/library_version_test.cpp.[Unreleased]→docs/changelog/v1/v1.1.0.md(+ index row);[Unreleased]reset.
docs/releases/v1.1.0.md(+ index row).What shipped in M11 (v1.1.0)
distribution/ABI policy · ADR-0031 security fuzzing + threat model + non-crypto hash scoping ·
benchmark targets ·
FlatMap::findwording + compile-verified constexpr example.EGL_UTIL_BUILD_FUZZERS+ thefuzzpreset. Header-only consumersunaffected.
Why MINOR
New opt-in surface, every existing use keeps working, no symbol removed/renamed/changed — the
maintenance decision tree says MINOR.
Verification
util_tests221/221 green incl. the bumped version assertions.python tools/consistency_lint.pypasses — version-lockstep acrossversion.hpp(1.1.0),the README badge,
docs/changelog/v1/v1.1.0.md, anddocs/releases/v1.1.0.md.Documentation Impact
choreMaintainer to-do (post-merge)
v1.1.0; push the annotated tagv1.1.0(if delegating thetag to the agent, say so).