Update README.md to incude python poetry #30
securestep9ci_cd.yml
on: push
Run pytest
18s
Test Docker image
7m 19s
Publish Docker image
55s
Annotations
2 errors and 5 warnings
|
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 (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:OWASP/Nettacker:ref:refs/heads/securestep9-poetry-readme-patch-1`
* `repository`: `OWASP/Nettacker`
* `repository_owner`: `OWASP`
* `repository_owner_id`: `155815`
* `job_workflow_ref`: `OWASP/Nettacker/.github/workflows/ci_cd.yml@refs/heads/securestep9-poetry-readme-patch-1`
* `ref`: `refs/heads/securestep9-poetry-readme-patch-1`
See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
|
|
Publish to Test 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 (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:OWASP/Nettacker:ref:refs/heads/securestep9-poetry-readme-patch-1`
* `repository`: `OWASP/Nettacker`
* `repository_owner`: `OWASP`
* `repository_owner_id`: `155815`
* `job_workflow_ref`: `OWASP/Nettacker/.github/workflows/ci_cd.yml@refs/heads/securestep9-poetry-readme-patch-1`
* `ref`: `refs/heads/securestep9-poetry-readme-patch-1`
See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
|
|
Run pytest
The following actions use a deprecated Node.js version and will be forced to run on node20: 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/
|
|
Build package
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Publish to PyPI
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/download-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Publish to Test PyPI
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/download-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "dist".
Please update your workflow to use v4 of the artifact actions.
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
dist
|
6.97 MB |
|