Skip to content

docs: document publish_release dispatch mechanics - #569

Merged
leoschwarz merged 1 commit into
mainfrom
docs/bfabric-scripts-1.15.1-note
Jul 30, 2026
Merged

docs: document publish_release dispatch mechanics#569
leoschwarz merged 1 commit into
mainfrom
docs/bfabric-scripts-1.15.1-note

Conversation

@leoschwarz

@leoschwarz leoschwarz commented Jul 30, 2026

Copy link
Copy Markdown
Member

The bfabric-scripts 1.15.1 hotfix (metadata-only cap of bfabric to <1.19, released off the bfabric_scripts/1.15.0 tag) surfaced three release-mechanics traps that weren't written down anywhere. This adds them to AGENTS.md:

  • environment: test is not a dry run. Create and push tag and Create GitHub Release are ungated and run before the publish step, so a test run consumes the tag and the production run then dies at git tag -a before reaching PyPI.
  • Verify a build offline with uv pip install --no-sources, and check entry points by module import rather than --help@use_client calls Bfabric.connect() before the wrapped function runs, so --help reads ~/.bfabricpy.yml first and can fail for reasons unrelated to the release.
  • GitHub keeps one repo-wide "Latest release", so a stable non-core release must not claim it. rcN and 0.x tags are auto-flagged prerelease and never compete for it.

It also corrects the hotfix convention. A hotfix whose fix can't apply to main has nothing to forward-port, and therefore nothing to add to main's changelog — an [Unreleased] bullet would be promoted into the next release's notes, describing a change that release doesn't contain. 1.15.1 is recorded by its tag and its published GitHub release.

🤖 Prepared with assistance from Claude Opus 5 via Claude Code.

@leoschwarz leoschwarz changed the title docs(bfabric_scripts): record the 1.15.1 hotfix release docs: record the 1.15.1 hotfix and the release-dispatch mechanics Jul 30, 2026
@leoschwarz
leoschwarz force-pushed the docs/bfabric-scripts-1.15.1-note branch from b1d4d20 to d777f86 Compare July 30, 2026 08:28
@leoschwarz leoschwarz changed the title docs: record the 1.15.1 hotfix and the release-dispatch mechanics docs: document publish_release dispatch mechanics Jul 30, 2026
Records what the bfabric_scripts 1.15.1 hotfix surfaced: an environment=test
"dry run" pushes the real tag and blocks the production run; entry points must
be verified by module import, since @use_client connects before argparse; and
GitHub's single repo-wide "Latest release" badge means a stable non-core
release must not claim it.

Also corrects the hotfix convention. A hotfix whose fix cannot apply to main
has nothing to forward-port and so nothing to put in main's changelog: an
[Unreleased] bullet would be promoted into the next release's notes,
describing a change that release does not contain.
@leoschwarz
leoschwarz force-pushed the docs/bfabric-scripts-1.15.1-note branch from d777f86 to 144d453 Compare July 30, 2026 08:30
@leoschwarz
leoschwarz marked this pull request as ready for review July 30, 2026 08:32
@leoschwarz
leoschwarz merged commit 3774666 into main Jul 30, 2026
24 checks passed
@leoschwarz
leoschwarz deleted the docs/bfabric-scripts-1.15.1-note branch July 30, 2026 08:34
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