Skip to content

Build, test, release #2

Build, test, release

Build, test, release #2

Triggered via create April 1, 2026 17:19
Status Failure
Total duration 46s
Artifacts 1

build-release.yml

on: create
call-build  /  Build distribution πŸ“¦
23s
call-build / Build distribution πŸ“¦
call-build  /  Version & tag the release
call-build / Version & tag the release
call-build  /  Publish Python 🐍 distribution πŸ“¦ to PyPI
14s
call-build / Publish Python 🐍 distribution πŸ“¦ to PyPI
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
call-build / Build distribution πŸ“¦
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
call-build / Publish Python 🐍 distribution πŸ“¦ to PyPI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
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):
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
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.

Artifacts

Produced during runtime
Name Size Digest
release-dist Expired
13.1 KB
sha256:d6fc59d443f4d65a09e3b46f7c3d7ac25f5c69b917007033008179b574afc22e