Repository navigation
build: release 5.0.1 - #410
Conversation
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
📊 SMDA Performance Evaluation Benchmark ResultsGenerated on: 2026-10-20 21:19:32 Summary
Per-side Timing Context (best of 3/3 runs per file)
Paired per-file timing (positive speedup = PR faster):
Determinism (self-check across repeated runs)
Pairwise run matrix (individual run medians, diagnostic)Diagnostic only: each row compares one raw PR run against one raw base run. The headline verdict above uses paired per-file best-of-runs timings.
|
Cuts 5.0.1:
__version__goes from 5.0.0 to 5.0.1.## [Unreleased]becomes## [v5.0.1] - 2026-10-20without its empty subsections (Added,Deprecated,Removed,Security,Compatibility). A fresh## [Unreleased]skeleton goes above it, and the compare links at the foot are updated. No changelog fixes were needed while cutting.Patch because the release carries a fix and a speed-up with identical reports. The version is a release counter, not semver. None of the three compatibility constants (
ESCAPER_DOWNWARD_COMPATIBILITY,INTEL_PIC_HASH_ESCAPE_VERSION,CIL_PIC_HASH_ESCAPE_VERSION) moved since v5.0.0.What 5.0.1 carries
Milestone
v5.0.1:TIMEOUT(fix(common): end the gap scan at the image end, not at the address mask #407).no-changelog).Checked before opening
gap_pointer == base + size.closure()on 20,000 random graphs.tyshows the same diagnostic count as master.testPackageMetadata.py,testReleaseGuard.pyandtestCommonModels.pypass on this branch (68 passed).release_guard.py --tag v5.0.1passes.python -m buildproduced a 435 KB sdist and a 475 KB wheel, andtwine check --strictpassed.Merge order
Merge #409 first so that the tag includes it, then this PR.
After merge
publish-release.ymlandrelease_guard.pyare unchanged since v5.0.0, so no TestPyPI rehearsal is needed. Once CI and the benchmark are green on the merge commit, tag it and push the tag:git tag -a v5.0.1 -m "SMDA 5.0.1" git push origin v5.0.1🤖 Generated with Claude Code