Skip to content

build: release 5.0.1 - #410

Merged
danielplohmann merged 1 commit into
masterfrom
build/release-5.0.1
Oct 20, 2026
Merged

danielplohmann merged 1 commit into
masterfrom
build/release-5.0.1

Conversation

@danielplohmann

Copy link
Copy Markdown
Owner

Cuts 5.0.1: __version__ goes from 5.0.0 to 5.0.1. ## [Unreleased] becomes ## [v5.0.1] - 2026-10-20 without 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:

Checked before opening

Merge order

Merge #409 first so that the tag includes it, then this PR.

After merge

publish-release.yml and release_guard.py are 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

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@danielplohmann danielplohmann added this to the v5.0.1 milestone Oct 20, 2026
@github-actions

Copy link
Copy Markdown

📊 SMDA Performance Evaluation Benchmark Results

Generated on: 2026-10-20 21:19:32

Summary

Metric Result
Correctness ✅ PASS — 0 / 155 common file(s) differ
Determinism ✅ PASS — base 3 run(s), PR 3 run(s)
Verdict inconclusive — within run-to-run noise (±2.3%)
Median paired speedup -0.42% (95% CI [-1.65%, +0.33%])
Timing noise band ±2.3%

Per-side Timing Context (best of 3/3 runs per file)

Side Files Functions Median best time/file (s) Sum of best times (s) Throughput estimate (func/s)
base 155 173540 0.6358 223.84 ~775
pr 155 173540 0.6075 222.96 ~778

These context rows sum each file's best observed time across repeated runs; they are normalized comparison estimates, not single-run CI wall-clock times.

Paired per-file timing (positive speedup = PR faster):

Statistic Value
Files compared 155
Median paired speedup -0.42% (95% CI [-1.65%, +0.33%])
Mean speedup -1.27% (95% CI [-2.26%, -0.30%])
Std dev / IQR 6.19% / 6.22%
Wilcoxon signed-rank p 0.8129 (n=155)

ℹ️ base and PR are timed in the same job on the same runner, with their passes interleaved base/PR/PR/base/base/PR so that drift over the job cancels rather than landing on whichever side ran last. The noise band above is therefore run-to-run variation on one machine, which is what it is able to measure; a difference inside it is reported as inconclusive. Correctness and determinism are not timing-based and are unaffected either way.

Determinism (self-check across repeated runs)

Side Runs Files Deterministic Median timing CV
base 3 155 ✅ 2.3%
pr 3 155 ✅ 1.8%
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.

Comparison Run PR Files Base Files Common Function Set Matches Med PR (s) Med Base (s) Med Diff (s) Speedup %
pr_0 vs base_0 155 155 155 155/155 0.6826s 0.6486s +0.0340s -5.24%
pr_0 vs base_1 155 155 155 155/155 0.6826s 0.6827s -0.0001s +0.02%
pr_0 vs base_2 155 155 155 155/155 0.6826s 0.6631s +0.0195s -2.95%
pr_1 vs base_0 155 155 155 155/155 0.6429s 0.6486s -0.0057s +0.88%
pr_1 vs base_1 155 155 155 155/155 0.6429s 0.6827s -0.0398s +5.83%
pr_1 vs base_2 155 155 155 155/155 0.6429s 0.6631s -0.0202s +3.04%
pr_2 vs base_0 155 155 155 155/155 0.6319s 0.6486s -0.0167s +2.58%
pr_2 vs base_1 155 155 155 155/155 0.6319s 0.6827s -0.0508s +7.45%
pr_2 vs base_2 155 155 155 155/155 0.6319s 0.6631s -0.0312s +4.70%

@danielplohmann
danielplohmann merged commit 04652e6 into master Oct 20, 2026
25 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant