ci(release): cut and publish releases from any branch, not only dev #119

Merged
peersky merged 2 commits from ci/release-from-any-branch into dev 2026-11-01 02:44:17 +00:00
Owner
  • Added ability to prepare a release from a named base branch (default dev) and open its release PR against that branch
  • Added ability to override the computed bump (auto/patch/minor/major), so a maintenance line can ship a patch over inherited feats
  • Fixed bug where the previous tag was the newest one in the repo rather than the newest on the release branch's history, and where pin tags counted as releases
  • Fixed bug where a version already released from another line would be reused; the next free patch is taken
  • Fixed bug where publish fired only for release PRs into dev, and a manual publish of a missing tag always tagged the default branch; it now takes an explicit ref
- Added ability to prepare a release from a named `base` branch (default dev) and open its release PR against that branch - Added ability to override the computed bump (auto/patch/minor/major), so a maintenance line can ship a patch over inherited feats - Fixed bug where the previous tag was the newest one in the repo rather than the newest on the release branch's history, and where pin tags counted as releases - Fixed bug where a version already released from another line would be reused; the next free patch is taken - Fixed bug where publish fired only for release PRs into dev, and a manual publish of a missing tag always tagged the default branch; it now takes an explicit `ref`
ci(release): cut and publish releases from any branch, not only dev
Some checks failed
CI / Dependency Age Check (pull_request) Successful in 7s
CI / Spell Check (pull_request) Successful in 6s
Commit Lint / Validate PR Title (pull_request) Successful in 4s
CI / Lint & Audit (pull_request) Failing after 2m4s
CI / Test (pull_request) Successful in 8m45s
e75e1f42a1
- Added ability to prepare a release from a named `base` branch (default dev) and open its release PR against that branch
- Added ability to override the computed bump (auto/patch/minor/major), so a maintenance line can ship a patch over inherited feats
- Fixed bug where the previous tag was the newest one in the repo rather than the newest on the release branch's history, and where pin tags counted as releases
- Fixed bug where a version already released from another line would be reused; the next free patch is taken
- Fixed bug where publish fired only for release PRs into dev, and a manual publish of a missing tag always tagged the default branch; it now takes an explicit `ref`
fix(deps): patch rustls, webpki and tokio advisories; record the unpatchable ones
All checks were successful
Commit Lint / Validate PR Title (pull_request) Successful in 5s
CI / Spell Check (pull_request) Successful in 6s
CI / Dependency Age Check (pull_request) Successful in 11s
CI / Lint & Audit (pull_request) Successful in 2m21s
CI / Test (pull_request) Successful in 6m11s
Publish Release / Create Tag & Sync (pull_request) Has been skipped
Publish Release / Publish to crates.io (pull_request) Has been skipped
Publish Release / Publish dry-run (no side effects) (pull_request) Has been skipped
Publish Release / Create GitHub Release (pull_request) Has been skipped
42628fa9de
- Fixed bug where rustls, rustls-webpki, webpki-roots, webpki-root-certs and tokio advisories (RUSTSEC-2026-0346..0349, -0381..0383, -0386) failed the audit; locked to patched releases
- Documented documentation of the advisories with no lockfile-sized fix in deny.toml, each with its removal condition (crypto-bigint 0.5.5 needs the k256 0.14 migration)
peersky deleted branch ci/release-from-any-branch 2026-11-01 02:44:18 +00:00
Sign in to join this conversation.
No reviewers
No labels
release
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
peeramid-labs/quorum-rs!119
No description provided.