Repository navigation
chore: cut v4.8.0rc1 - #347
Conversation
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
📊 SMDA Performance Evaluation Benchmark ResultsGenerated on: 2026-09-14 13:53:29 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.
|
The release candidate that rehearses #343's workflow. No code changes:
__version__moves to4.8.0rc1and## [Unreleased]becomes## [v4.8.0rc1] - 2026-09-14.This exists to run the release path once before a real version number is at stake. Two defects have already come out of preparing it — #345 and #346 — and neither was reachable without trying to cut a candidate.
What it carries
Five entries, each written by its author at merge time:
Added — the release-on-a-tag workflow (#343).
Changed —
SmdaConfig.VERSIONread fromsmda.__version__, and the PEP 639 licence expression with the project URLs (#343).Deprecated — the 3.11 support policy: the floor follows MCRIT's and moves in the same wave (#343).
Fixed — a pre-release version is now ordered on report import rather than treated as no version at all (#345).
Removed,SecurityandCompatibilitywere empty and are dropped. A fresh## [Unreleased]sits above with the full scaffold. None of the three compatibility constants moved, so noCompatibilitysection is owed.Why a candidate rather than going straight to v4.8.0
Pushing any
v*tag runs the real path to PyPI, and a manual TestPyPI run needs the tag to already exist on the remote — so pushing is both what makes a rehearsal possible and what would publish it. The required reviewer on thepypienvironment is what separates the two: the push run stops at the publish job for approval, that gets rejected, and the same tag is then dispatched manually to TestPyPI.A version number on PyPI is permanent even when yanked. Spending
4.8.0rc1to find out whether the workflow holds is the cheap way to learn it.Verification
On this branch, saturn:
python -m pytest tests/→ 2,172 passed, 1 skipped, 2,623 subtestsruff check .andruff format --check .→ cleanrelease_guard.py --tag v4.8.0rc1→ passes,version=4.8.0rc1 prerelease=true, so the GitHub release for it would be marked a pre-release and never become latest[Unreleased]spansv4.8.0rc1...HEAD,[v4.8.0rc1]spansv4.7.0...v4.8.0rc1After the rehearsal
The final cut renames
## [v4.8.0rc1]to## [v4.8.0] - <date>rather than adding a second section repeating it — the candidate's own release notes were generated from the tree at its tag, so nothing is lost by the heading moving on.RELEASING.mddoes not currently say which of those two it wants; worth settling there once the rehearsal has shown what the notes actually look like.🤖 Generated with Claude Code