Skip to content

Merge pull request #598 from ngageoint/staging #4

Merge pull request #598 from ngageoint/staging

Merge pull request #598 from ngageoint/staging #4

Triggered via push August 15, 2025 20:08
Status Failure
Total duration 40s
Artifacts 1

build.yml

on: push
Matrix: Build distribution
Create release
6s
Create release
Publish to PyPI
9s
Publish to PyPI
Fit to window
Zoom out
Zoom in

Annotations

1 error
Publish to PyPI
Trusted publishing exchange failure: Token request failed: the server refused the request for the following reasons: * `invalid-publisher`: valid token, but no corresponding publisher (Publisher with matching claims was not found) 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:ngageoint/sarpy:environment:development` * `repository`: `ngageoint/sarpy` * `repository_owner`: `ngageoint` * `repository_owner_id`: `7175944` * `workflow_ref`: `ngageoint/sarpy/.github/workflows/build.yml@refs/heads/master` * `job_workflow_ref`: `ngageoint/sarpy/.github/workflows/build.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 Digest
1.3.61.1 Expired
2.7 MB
sha256:c91724494a314fe863a2eb97e6e1df154f7a342757af04c2da220a9d15886a0f