Skip to content

Fix nox venv reuse issue (#811) #431

Fix nox venv reuse issue (#811)

Fix nox venv reuse issue (#811) #431

Triggered via push April 22, 2026 19:01
Status Success
Total duration 32s
Artifacts

release.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
Release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: release-drafter/release-drafter@v6.1.0, salsify/action-detect-and-tag-new-version@v2.0.3. 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/
Release
Input 'repository_url' has been deprecated with message: The inputs have been normalized to use kebab-case. Use `repository-url` instead.
Release
"pull_request_target.edited" is not a known webhook name (https://developer.github.com/v3/activity/events/types/)
Release
"pull_request_target.synchronize" is not a known webhook name (https://developer.github.com/v3/activity/events/types/)
Release
"pull_request_target.reopened" is not a known webhook name (https://developer.github.com/v3/activity/events/types/)
Release
"pull_request_target.opened" is not a known webhook name (https://developer.github.com/v3/activity/events/types/)
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.
Release
Input 'repository_url' has been deprecated with message: The inputs have been normalized to use kebab-case. Use `repository-url` instead.