Skip to content

release-plz: allow our own just-published siblings during resolution #33

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
proggeramlug merged 1 commit into from
Sep 15, 2026
Merged

release-plz: allow our own just-published siblings during resolution #33

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
7 changes: 7 additions & 0 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -91,6 +91,13 @@ jobs:
env:
GIT_TOKEN: ${{ steps.app.outputs.token }}
RUSTUP_TOOLCHAIN: nightly-2026-08-20
# release-plz resolves each crate against the registry, where our own
# siblings are hours old, so the seven-day publish-age soak rejects
# them ("turnloop-io = ^0.1.0-alpha.3 is too new"). The soak exists for
# third-party supply chain, and this resolution produces no artifact:
# every lockfile the release PR carries is still gated by
# scripts/ci/soak.py in required CI, which no exception here can skip.
CARGO_RESOLVER_INCOMPATIBLE_PUBLISH_AGE: allow
run: release-plz release-pr --repo-url https://github.com/PerryTS/turnloop --config release-plz.toml
dispatch-publish:
needs: verify
Expand Down