Skip to content

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

Merged
Jammy2211 merged 1 commit into
mainfrom
feature/release-stamping-slim
Jul 8, 2026
Merged

feat: release stamping slim — wheels+tags only, no daily bump commits (R3-core)#121
Jammy2211 merged 1 commit into
mainfrom
feature/release-stamping-slim

Conversation

@Jammy2211

Copy link
Copy Markdown
Collaborator

⛔ Merge gate

Merge PyAutoLabs/PyAutoConf#119 (compatibility-floor version check) first. The release that stops writing workspace version 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.

Overview

R3-core of the version-pinning design review (#118; task issue #120). Releases become wheels + tags only: no more daily "Update version to X" commits to five library mains, no more "pin workspace version" / README-stamp commits to every workspace main — the stale-CI/email noise engine behind the June/July accidental-release cascade. Also removes the scheduled run_number version fallback that produced the 2026.6.25.641 → 2026.7.6.649 accidental series.

Issue: #120 · Design review: #118

Changes (.github/workflows/release.yml, docs/internals.md)

  1. version_number: scheduled runs default the minor to 1 (<date>.1), never github.run_number, in both live and rehearsal compositions. 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. release job: the sed version stamp still runs (wheels carry the version) but is no longer committed back; branch git push dropped, git push --tags kept — tags remain the release anchor for Colab URLs and workspace pairing.
  3. release_workspaces: "Update version in README" and "Write workspace version" (version.txt + general.yaml) steps removed — obsolete under the floor check. Notebook regen, Colab bumps, API baseline, and workspace tags untouched (their cadence under daily live releases is Q2 on research: version-pinning design review — exact pins vs daily release #118, decided separately).
  4. docs/internals.md pure-executor and version-skew paragraphs updated to match.

Test Results

  • tests/: 71 passed. Workflow YAML parses clean.
  • Grepped for consumers of the removed steps: none in autobuild/; PyAutoHeart's version_skew check reads the now-frozen artifacts and stays functional-but-inert during the transition — its floor-vs-tag rework is a filed follow-up.

Ship gate

Supervised --auto run; maintainer sign-off + Heart YELLOW acknowledgement (same 6-reason set as PyAutoConf#119's gate) given in-session on 2026-07-08 ("continue --auto" following the surfaced sign-off summary).

🤖 Generated with Claude Code

https://claude.ai/code/session_01WGkd3Jf7tjNpWqeU27aShB

Scheduled releases version as <date>.1, never <date>.<run_number> (the
2026.6.25.641->649 accidental-series mechanism). The release job stamps
__init__.py in the build tree without committing back; branch push dropped,
tag push kept. release_workspaces no longer writes version.txt /
general.yaml pins or README version stamps (obsolete under the
compatibility-floor check, PyAutoConf#118). Notebook regen, Colab bumps,
API baseline and workspace tags unchanged.

R3-core of the version-pinning design review (#118).
Issue: #120

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WGkd3Jf7tjNpWqeU27aShB
@Jammy2211 Jammy2211 added the pending-release Merged PR awaiting inclusion in the next release build label Jul 8, 2026
@Jammy2211 Jammy2211 merged commit 0cb207f into main Jul 8, 2026
@Jammy2211 Jammy2211 deleted the feature/release-stamping-slim branch July 8, 2026 20:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pending-release Merged PR awaiting inclusion in the next release build

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant