Skip to content
Create library release archives, create a GH release and publish PyPI wheel and sdist on tag in main branch

Merge pull request #19 from aboutcode-org/build-src #8

Sign in to view logs

Merge pull request #19 from aboutcode-org/build-src

Merge pull request #19 from aboutcode-org/build-src #8

Triggered via push November 5, 2024 20:31
@JonoYangJonoYang
pushed 442bc5b
v0.5.0
Status Success
Total duration 1m 36s
Artifacts 1

pypi-release.yml

on: push
Build and publish library to PyPI
30s
Build and publish library to PyPI
Create GH release
11s
Create GH release
Create PyPI release
37s
Create PyPI release
Fit to window
Zoom out
Zoom in

Annotations

7 warnings
Build and publish library to PyPI
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, 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/
Create GH release
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/download-artifact@v3, softprops/action-gh-release@v1. 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: "pypi_archives". 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/
Create PyPI release
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/
attestations input ignored
The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
Create a Trusted Publisher
A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):

Artifacts

Produced during runtime
Name Size
pypi_archives
55 MB