Move version.py into package dir; replace workflows with shared gh-automations callers #1
JarbasAlrelease_workflow.yml
on: pull_request
publish_alpha
/
bump_version
9s
publish_alpha
/
notify
4s
publish_alpha
/
tag_prerelease
6s
publish_alpha
/
propose_release
6s
publish_alpha
/
publish_pypi
21s
Annotations
2 errors and 4 warnings
|
publish_alpha / notify
Process completed with exit code 22.
|
|
publish_alpha / update_changelog
No valid releases
|
|
publish_alpha / update_changelog
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pozetroninc/github-action-get-latest-release@v0.8.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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.
|