Skip to content

Python Release

Python Release #17

Re-run triggered June 25, 2024 22:08
Status Failure
Total duration 7m 26s
Artifacts 4

release-python.yml

on: workflow_dispatch
pre-publish
43s
pre-publish
Matrix: build-dist / build_dist
static-scan  /  Analyze Python
2m 23s
static-scan / Analyze Python
build-dist  /  Collect dist files
4s
build-dist / Collect dist files
Fit to window
Zoom out
Zoom in

Deployment protection rules

Reviewers, timers, and other rules protecting deployments in this run
Event Environments Comment
blink1073
approved Jun 25, 2024
release-python
blink1073
approved Jun 25, 2024
release-python

Annotations

2 errors
build-dist / build_dist (macos-latest)
[notice] A new release of pip is available: 21.1.1 -> 24.1 [notice] To update, run: python3.8 -m pip install --upgrade pip
publish
Trusted publishing exchange failure: Token request failed: the server refused the request for the following reasons: * `invalid-publisher`: valid token, but no corresponding publisher (All lookup strategies exhausted) This generally indicates a trusted publisher configuration error, but could also indicate an internal error on GitHub or PyPI's part. The claims rendered below are **for debugging purposes only**. You should **not** use them to configure a trusted publisher unless they already match your expectations. If a claim is not present in the claim set, then it is rendered as `MISSING`. * `sub`: `repo:mongodb/libmongocrypt:environment:release-python` * `repository`: `mongodb/libmongocrypt` * `repository_owner`: `mongodb` * `repository_owner_id`: `45120` * `job_workflow_ref`: `mongodb/libmongocrypt/.github/workflows/release-python.yml@refs/heads/master` * `ref`: `refs/heads/master` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.

Artifacts

Produced during runtime
Name Size
all-dist-9670016215 Expired
19.8 MB
dist-macos-latest Expired
6.66 MB
dist-ubuntu-latest Expired
10.6 MB
dist-windows-latest Expired
2.56 MB