Skip to content

docs: plan signer-aligned +signer release versions #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mstattma merged 1 commit into from
Oct 16, 2026
Merged

docs: plan signer-aligned +signer release versions #7

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions docs/release-notes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,18 @@
# Release notes

## Planned: signer-aligned release versions

Decided 2026-10-16, effective from the next release built for a signer release
(signer `1.0.8` uses `0.37.13.dev2`). Such releases use a PEP 440 local version
naming the signer version, `<castlabs-base>+signer.<signer-version>[.<n>]`, for
example `0.37.14+signer.1.0.9`, tagged `castlabs-v0.37.14+signer.1.0.9`. They are
final, immutable GitHub releases (`prerelease=false`), not published to PyPI
(local versions are rejected there). Development builds keep `.devN` versions,
and the development line moves to the next `.devN` series after each aligned
release. A signer retry under a new version gets a new `+signer` release.
Release-tooling changes (escaped tag trigger, prerelease flag, artifact names,
PyPI workflow limited to `.devN`) land with that release.

## Version 0.37.13.dev2

Castlabs VSI prerelease (tag `castlabs-v0.37.13.dev2`, released from
Expand Down
Loading