feat: release stamping slim — wheels+tags only, no daily bump commits (R3-core)

[Jammy2211]

Overview

R3-core of the version-pinning design review (#118). Every release pushes "Update version to X" commits to all five library mains and "pin workspace version" / README-stamp commits to every workspace main — the noise engine behind the June/July accidental-release cascade (stale CI storms, email flood, org-wide cron pause). The wheels already get their version from sed at build time, so none of these commit-backs are needed for published artifacts. This task makes releases wheels+tags-only, and removes the scheduled run_number version fallback that produced the 2026.6.25.641 → 2026.7.6.649 accident.

Autonomy: --auto, effective supervised (feature cap — deliberate behavior change, not a pure refactor). Plan recorded here; ship sign-off will park with a batched question.

Plan

• Scheduled releases version as <date>.1, never <date>.<run_number> (rehearsal uniqueness already comes from the .devN segment).
• release job: keep build-tree sed stamp + annotated tag + git push --tags; drop the __init__.py commit-back and branch push to library mains.
• release_workspaces: drop the "Write workspace version" step (obsolete under PyAutoConf#118 floor semantics) and the README version-stamp commit; keep notebook regen, Colab bumps, API baseline, workspace tags (their cadence is Q2 on research: version-pinning design review — exact pins vs daily release #118, decided separately).
• Merge gate: merge only after PyAutoConf#118 (R2), so the release that stops writing pins also ships the floor check.

Detailed implementation plan

Affected Repositories

• PyAutoBuild (only)

Branch Survey

Repository	Current Branch	Dirty?
./PyAutoBuild	main	clean

Note: active.md still carries a PyAutoBuild claim from morning-status-release-rehearsal, but all three of its PRs (Build#119, Heart#40, Mind#41) are merged — the claim is stale post-merge state, recorded here rather than deleting another session's entry.

Suggested branch: feature/release-stamping-slim
Worktree root: ~/Code/PyAutoLabs-wt/release-stamping-slim/

Implementation Steps

1. .github/workflows/release.yml version_number job: VERSION="${DATE_FORMATTED}.${MINOR_VERSION:-1}" (both the live and rehearsal composition lines) — a same-day manual dispatch after a scheduled live release must pick its own minor_version (twine will loudly reject a duplicate otherwise).
2. release job: delete the Update version step's git commit; in Tag, drop git push (branch), keep git push --tags. The sed stamps stay (they version the build tree that produces the wheels; pyproject.toml sibling-pin sed unchanged).
3. release_workspaces: delete the Update version in README and Write workspace version steps; leave notebook regen / Colab bumps / API baseline / tag-and-push untouched.
4. Sanity: python -m pytest tests/ in PyAutoBuild; YAML-parse the workflow; grep the repo for consumers of the removed steps (verify_workspace_versions already removed in Add a release-execution skills root (pre_build) #110-era cleanup).

Key Files

• PyAutoBuild/.github/workflows/release.yml

Out of scope (follow-ups)

• Q2 on research: version-pinning design review — exact pins vs daily release #118: notebook/Colab cadence under daily live releases.
• Library __version__ via importlib.metadata (parked to avoid conflicting with the in-flight PyAutoConf#118 worktree).
• PyAutoHeart version_skew rework for floor semantics (compares workspace pins vs __init__ stamps; goes inert once both freeze — needs a new signal source, e.g. floor vs latest tag).

Original Prompt

Click to expand starting prompt

R3 of PyAutoBuild#118 (endorsed 2026-07-08): stop committing version bumps to main on every release — the wheel already gets its version from the VERSION env var at build time; runtime __version__ can come from importlib.metadata. Keep the git tags (they anchor Colab URLs and releases); drop the daily "Update version to X" / "pin workspace version" / Colab-bump commits, which were the noise-and-stale-CI engine of the incident. Plus the #39 residue: MINOR_VERSION still falls back to github.run_number on scheduled runs — R3 defaults it to 1 on schedule.

User go-ahead: "ok, those PRs are done so we can do this work now --auto"

[Jammy2211]

Ship sign-off (supervised --auto: parked here, uncommitted in the worktree)

Implementation complete and validated.

What changed (.github/workflows/release.yml + docs/internals.md)

1. No more run-number versions: scheduled runs default the minor to 1 (<date>.1), in both the live and rehearsal version compositions — the 2026.6.25.641→649 accident mechanism is gone. Rehearsal uniqueness still comes from the .devN segment. A same-day manual dispatch after a scheduled live release must pick its own minor_version (twine rejects duplicates loudly — stated in a comment).
2. Library mains untouched by releases: the release job still sed-stamps __init__.py in the build tree (wheels carry the version) but no longer commits it back; the branch git push is dropped, git push --tags kept — tags remain the release anchor.
3. Workspace version pins gone: release_workspaces drops the "Update version in README" and "Write workspace version" (version.txt + general.yaml) steps. Notebook regen, Colab bumps, API baseline, and workspace tags are untouched (cadence = Q2 on research: version-pinning design review — exact pins vs daily release #118, still open).
4. docs/internals.md updated to match (pure-executor description + version-skew paragraph, noting the Heart version_skew follow-up).

Net: a live daily release now writes zero commits to library mains and only notebook/Colab content commits to workspaces — the stale-CI/email noise engine is removed.

Validation

• tests/: 71 passed. Workflow YAML parses clean. Grepped for consumers of the removed steps: none in autobuild/ (the old verify_workspace_versions pre_build step was already removed); Heart's version_skew reads the frozen artifacts and stays functional-but-inert during transition (follow-up filed when this ships).

Merge gate (hard)

Merge PyAutoConf#118 (R2 floor check) first — the release that stops writing pins must also ship floor semantics, so the last-stamped workspace_version values behave as floors, not exact-match tripwires. Both are pending-release; one release window carries both.

Heart

YELLOW (score 42, same 6 reasons as PyAutoConf#118's sign-off; no launch ack) → parked per the contract.

On approval

Commit on feature/release-stamping-slim, push, open PR to PyAutoBuild main (marked merge-after-PyAutoConf#118). Answer options: (a) "ship it" (Heart YELLOW reasons acknowledged); (b) request changes; (c) hold.

[Jammy2211]

Shipped at PR-open: #121 (commit e912219, 71 tests pass, labeled pending-release). Maintainer sign-off + Heart YELLOW acknowledgement (same 6-reason set) given in-session 2026-07-08 via "continue --auto". Merge gate: merge PyAutoConf#119 first.

[Jammy2211]

Merged as #121 (2026-07-08), after its merge gate PyAutoConf#119. From the next release onward: scheduled versions are <date>.1, library mains receive no version-bump commits, workspaces receive no version pins. Q2 on #118 resolved: notebook regen + Colab bumps keep their per-release cadence (already preserved by this PR — no further change).