Skip to content

Disable release creation workflow on forks #971

Disable release creation workflow on forks

Disable release creation workflow on forks #971

Triggered via pull request July 29, 2024 12:35
@gbruningbrunin
synchronize #940
Matgenix:main
Status Failure
Total duration 5m 2s
Artifacts

test.yml

on: pull_request
Matrix: test
auto-gen-release
0s
auto-gen-release
Fit to window
Zoom out
Zoom in

Annotations

1 error and 4 warnings
test (3.11, 4.0)
Process completed with exit code 1.
test (3.10, 4.0)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test (3.9, 4.0)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test (3.9, 4.0): # >> PyPA publish to PyPI GHA: POTENTIALLY INVALID TOKEN <<#L1
It looks like you are trying to use an API token to authenticate in the package index and your token value does not start with "pypi-" as it typically should. This may cause an authentication error. Please verify that you have copied your token properly if such an error occurs.
test (3.11, 4.0)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/