From ef4d315994308f1e795fd2d45196df7f5f1929e5 Mon Sep 17 00:00:00 2001 From: Ahmed Ibrahim Date: Fri, 8 May 2026 21:28:11 +0300 Subject: [PATCH] Make Python runtime publish non-blocking Allow the Rust release workflow to finish even if the new Python runtime PyPI publish job needs follow-up. Co-authored-by: Codex --- .github/workflows/rust-release.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/.github/workflows/rust-release.yml b/.github/workflows/rust-release.yml index d78330be7a..f0f7f4b7c6 100644 --- a/.github/workflows/rust-release.yml +++ b/.github/workflows/rust-release.yml @@ -853,13 +853,16 @@ jobs: done # Publish the platform-specific Python runtime wheels using PyPI trusted publishing. - # PyPI project configuration must trust this workflow and job. + # PyPI project configuration must trust this workflow and job. Keep this + # non-blocking while the Python runtime publishing path is new; failures still + # need release follow-up, but should not invalidate the Rust release itself. publish-python-runtime: # Publish to PyPI for stable releases and alpha pre-releases with numeric suffixes. if: ${{ needs.release.outputs.should_publish_python_runtime == 'true' }} name: publish-python-runtime needs: release runs-on: ubuntu-latest + continue-on-error: true environment: pypi permissions: id-token: write # Required for PyPI trusted publishing.