From b6c38f836521597defa1c38d12b6b215381e672c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ralph=20K=C3=BCpper?= Date: Tue, 15 Sep 2026 15:06:52 +0200 Subject: [PATCH] release-plz: allow our own just-published siblings during resolution main CI run after #32 failed in release-pr: release-plz runs cargo update per crate, which resolves siblings from the registry, and the seven-day soak rejects versions we published hours earlier ('turnloop-io = ^0.1.0-alpha.3 is too new'). Caret requirements (#25) made this reachable; exact pins hid it. The soak protects third-party supply chain, and this resolution produces no artifact: any lockfile the release PR carries is still gated by scripts/ci/soak.py in required CI, which this step cannot bypass. --- .github/workflows/release.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index ce508db..eb2246e 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -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