You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Browse filesBrowse the repository at this point in the historyBrowse files
committed
fix: only lock on published releases, keep updating drafts
The draft release is a staging area that gets continuously replaced as
main evolves. Only a published (non-draft) release acts as a lock:
- prepare-release: skips only when a published release exists for the
version (meaning it is already on PyPI). Draft releases are freely
overwritten by force-updating the release branch.
- release-artifacts: creates or replaces the draft after every green
test run. Skips only when a published release exists.
To start a fresh release cycle after publishing, the next push to main
with new fragments will compute a new version automatically.
Co-authored-by: Cursor AI <ai@cursor.sh>
Co-authored-by: Anthropic Claude Opus 4 <claude@anthropic.com>
0 commit comments