Skip to content

chore: cut v4.8.0 - #348

Merged
danielplohmann merged 1 commit into
masterfrom
chore/release-v4.8.0
Sep 14, 2026
Merged

danielplohmann merged 1 commit into
masterfrom
chore/release-v4.8.0

Conversation

@danielplohmann

Copy link
Copy Markdown
Owner

The release the v4.8.0rc1 rehearsal was for. No code changes: __version__ moves to 4.8.0 and the candidate's section becomes ## [v4.8.0] - 2026-09-14.

What it carries

Four merged PRs, one topic: releasing is now something the repository does rather than something a person remembers.

Added — pushing a vX.Y.Z tag builds, publishes to PyPI through trusted publishing, creates the GitHub release from this version's changelog section, and closes the milestone; five gates refuse to publish otherwise (#343).
Changed — SmdaConfig.VERSION read from smda.__version__ so a release bumps one line, and the PEP 639 licence expression with the project URLs (#343).
Deprecated — the Python 3.11 policy: the floor follows MCRIT's and the two move in the same wave (#343).
Fixed — a pre-release version is ordered on report import instead of being treated as no version at all (#345).

Removed, Security and Compatibility are dropped as empty. No compatibility constant moved, verified against the v4.7.0 tag rather than inferred from the entries, so this release owes no Compatibility section.

The candidate's heading is renamed rather than a second section added. v4.8.0rc1's own notes were generated from the tree at its tag, so nothing is lost by the heading moving on, and the changelog keeps one entry per version a user can install. Its [v4.8.0rc1] link definition goes with it rather than being left dangling.

tests/testPackageMetadata.py (#346) carries no entry: test-only, nothing under src/smda/ or pyproject.toml moved.

What the rehearsal established

v4.8.0rc1 ran the whole path on 2026-09-14. Both halves of the gate behaved:

  • The push run stopped at the pypi environment and was rejected. Verify and build both passed, publish failed on the rejection, and the release job skipped — no GitHub release, no milestone touched, nothing on PyPI. A rejected deployment leaves no partial state.
  • The dispatch run published to TestPyPI and stopped, exactly as a rehearsal should. TestPyPI still reports latest: 1.1.1, which is the pre-release marking working end to end rather than only in the guard's output.
  • Installed from TestPyPI into a clean venv and run with python -P: 33 functions on cutwail_xored, smda_version: 4.8.0rc1, and re-importing that report costs 0 recalculations with hashes intact. That is fix(common): order a pre-release version when importing a report #345 confirmed on an artifact a user could install, not only in the suite.

The milestone gate is the one thing the rehearsal did not exercise — no milestone was named v4.8.0rc1, so it reported a notice and continued. A v4.8.0 milestone now exists reading 0 open / 4 closed, so this release runs that gate for real.

Verification

On this branch, saturn:

  • python -m pytest tests/ → 2,172 passed, 1 skipped, 2,623 subtests
  • ruff check . and ruff format --check . → clean
  • release_guard.py --tag v4.8.0 → passes, version=4.8.0 prerelease=false
  • compare links: [Unreleased] spans v4.8.0...HEAD, [v4.8.0] spans v4.7.0...v4.8.0

After this merges and master is green, the tag goes on and the deployment gets approved rather than rejected. That publish is the first one this repository has made without a person holding an API token.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@danielplohmann danielplohmann added this to the v4.8.0 milestone Sep 14, 2026
@github-actions

Copy link
Copy Markdown

📊 SMDA Performance Evaluation Benchmark Results

Generated on: 2026-09-14 14:51:22

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 (±7.8%)
Median paired speedup -0.72% (95% CI [-1.84%, +0.35%])
Timing noise band ±7.8%

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 173496 0.7452 283.03 ~613
pr 155 173496 0.6944 284.53 ~610

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.72% (95% CI [-1.84%, +0.35%])
Mean speedup -4.14% (95% CI [-8.04%, -0.67%])
Std dev / IQR 23.36% / 8.50%
Wilcoxon signed-rank p 0.2507 (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 ✅ 7.8%
pr 3 155 ✅ 6.6%
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.9390s 0.9399s -0.0010s +0.10%
pr_0 vs base_1 155 155 155 155/155 0.9390s 0.9848s -0.0459s +4.66%
pr_0 vs base_2 155 155 155 155/155 0.9390s 0.9547s -0.0157s +1.64%
pr_1 vs base_0 155 155 155 155/155 0.9417s 0.9399s +0.0018s -0.19%
pr_1 vs base_1 155 155 155 155/155 0.9417s 0.9848s -0.0432s +4.38%
pr_1 vs base_2 155 155 155 155/155 0.9417s 0.9547s -0.0130s +1.36%
pr_2 vs base_0 155 155 155 155/155 0.9223s 0.9399s -0.0176s +1.87%
pr_2 vs base_1 155 155 155 155/155 0.9223s 0.9848s -0.0625s +6.35%
pr_2 vs base_2 155 155 155 155/155 0.9223s 0.9547s -0.0324s +3.39%

@danielplohmann
danielplohmann merged commit 9879aa7 into master Sep 14, 2026
47 checks passed
@danielplohmann
danielplohmann deleted the chore/release-v4.8.0 branch September 14, 2026 14:54
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