Skip to content

Release Build

Release Build #3

Manually triggered March 14, 2024 18:46
Status Failure
Total duration 1m 59s
Artifacts 2

build-release.yml

on: workflow_dispatch
release  /  ...  /  validate-event-details
3s
release / metadata / validate-event-details
release  /  ...  /  construct-payload
8s
release / metadata / construct-payload
release  /  ...  /  get-dependency-details
2s
release / metadata / get-howso-synthesizer-py-details / get-dependency-details
release  /  ...  /  get-dependency-details
2s
release / metadata / get-howso-validator-enterprise-py-details / get-dependency-details
release  /  ...  /  get-dependency-details
3s
release / metadata / get-howso-validator-py-details / get-dependency-details
release  /  ...  /  get-dependency-details
3s
release / metadata / get-howso-engine-py-details / get-dependency-details
release  /  ...  /  get-dependency-details
5s
release / metadata / get-amalgam-lang-py-details / get-dependency-details
release  /  ...  /  get-dependency-details
2s
release / metadata / get-howso-engine-details / get-dependency-details
release  /  ...  /  get-dependency-details
2s
release / metadata / get-amalgam-details / get-dependency-details
release  /  ...  /  set-metadata
2s
release / metadata / set-metadata
release  /  ...  /  set-version
7s
release / metadata / set-version
release  /  release
25s
release / release
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
release / release
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:howsoai/howso-engine-no-telemetry:environment:pypi` * `repository`: `howsoai/howso-engine-no-telemetry` * `repository_owner`: `howsoai` * `repository_owner_id`: `138059857` * `job_workflow_ref`: `howsoai/howso-engine-no-telemetry/.github/workflows/build.yml@refs/heads/main` * `ref`: `refs/heads/main` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
release / build
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
release / release
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/download-artifact@v3, actions/setup-python@v4. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Artifacts

Produced during runtime
Name Size
howso-engine-no-telemetry-1.1.3 Expired
39.8 KB
howso_engine_no_telemetry-1.1.3-py3-none-any Expired
25.4 KB