Skip to content

Fixing the publish pipeline. #2

Fixing the publish pipeline.

Fixing the publish pipeline. #2

Triggered via push September 4, 2024 03:58
Status Failure
Total duration 1m 4s
Artifacts 2

publish.yaml

on: push
provenance  /  detect-env
5s
provenance / detect-env
provenance  /  generator
12s
provenance / generator
provenance  /  upload-assets
0s
provenance / upload-assets
provenance  /  final
0s
provenance / final
create-release
3s
create-release
publish-pypi
0s
publish-pypi
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 3 warnings
publish-pypi
Tag "v0.1.1" is not allowed to deploy to publish due to environment protection rules.
publish-pypi
The deployment was rejected or didn't satisfy other protection rules.
build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
provenance / generator
Restore cache failed: Dependencies file is not found in /home/runner/work/assists/assists. Supported file pattern: go.sum
provenance / generator
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@93397bea11091df50f3d7e59dc26a7711a8bcfbe. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Artifacts

Produced during runtime
Name Size
artifact
13 KB
multiple.intoto.jsonl Expired
4.93 KB