Repository navigation
Prepare the stable 1.0.0 release - #38
Merged
Merged
Conversation
This was referenced Sep 11, 2026
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.
Outcome
Prepare the stable
1.0.0release without publishing it.Part of #24.
Changes
## [1.0.0] - 2026-09-11.owner's accepted exact-stable-target route without
rc.2.independent review evidence.
No runtime, public API, dependency, platform, workflow, test, localdev, or
package-policy source changes are included.
Release intent
1.0.02026-09-111.0.0-rc.1057ad95f9a44421bf24dd795d8a39bf132daac1ce19fa44b7fe5a754a47c2fa31.0.0: confirmed absent during preparation.This PR does not dispatch the Release workflow and does not authorize
publish=true.Verification
make checkmake coveragemake test.package-installmake smokeminimum-20260911T165030Z-7801-192latest-20260911T165104Z-8804-1252541f2403996669d2ad866ae0a74013407c0aa09a8, 82,248 bytes, SHA-25606717daaed545b3d7f12aa123944d7a19f81a7ae680bf2ae150d6ffc974294448694c9e27adcd90f384a98c52a22b0c4dfdc51c1, 82,772 bytes, SHA-25658bf5f6503b687e462342d3c68c4a24e1683a1542199fe78e6e5372181eb9387Each hosted ZIP passed the same complete three-artifact runner: exact target,
eight allowed roots, installed public-symbol provenance, frozen 19-method API
and private seams, classmap-authoritative no-dev install, and zero development
packages.
Independent review
Independent E5 preparation QA reviewed exact commit
41f2403against base26f4d03, repeated the release-intent and proportionate test gates, and foundzero blocker, high, medium, or low findings. The subsequent commit changes only
the delivery-plan evidence and the exact pushed head passed the hosted package
gate again.
Remaining gates
master.publish=falsefor exact1.0.0/ merged full SHA / current UTC date.publish=true.If the UTC date changes before the dry run, the changelog date and release tuple
must be updated in a new reviewed commit.