Skip to content

fix: list release branch in workflow (#193) #12

fix: list release branch in workflow (#193)

fix: list release branch in workflow (#193) #12

Triggered via push March 12, 2026 15:15
Status Failure
Total duration 3m 19s
Artifacts 2
build-release  /  ...  /  check-tag
4s
build-release / check-tag-privilege / check-tag
build-release  /  ...  /  check-privilege
2s
build-release / check-tag-privilege / check-privilege
build-release  /  ...  /  validate-pat-token
10s
build-release / check-pat-token-validity / validate-pat-token
build-release  /  ...  /  validate-pypi-token
3s
build-release / check-pypi-token-validity / validate-pypi-token
build-release  /  ...  /  get-python-versions
11s
build-release / get-python-version / get-python-versions / get-python-versions
build-release  /  ...  /  extract-latest
3s
build-release / get-python-version / extract-latest
build-release  /  ...  /  build
22s
build-release / build-wheel / python-pure / build
build-release  /  ...  /  Build sdist
build-release / build-wheel / python-extension / Build sdist
Matrix: build-release / build-wheel / python-extension / build-wheel
Waiting for pending jobs
Matrix: build-release / build-wheel / python-extension / test-wheels
Waiting for pending jobs
build-release  /  ...  /  pre-release
7s
build-release / release-github / pre-release
build-release  /  ...  /  release-update-changelog
build-release / release-github / release-update-changelog
build-release  /  ...  /  release-delete-create-new-tag
build-release / release-github / release-delete-create-new-tag
build-release  /  ...  /  release
build-release / release-github / release
build-release  /  ...  /  release
12s
build-release / release-pypi / release
build-release  /  ...  /  build-deploy
2m 5s
build-release / docs-release / build-deploy
Fit to window
Zoom out
Zoom in

Annotations

1 error and 9 warnings
build-release / release-pypi / release
Process completed with exit code 1.
build-release / check-pat-token-validity / validate-pat-token
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
build-release / get-python-version / get-python-versions / get-python-versions
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
build-release / build-wheel / python-pure / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
build-release / release-github / pre-release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: softprops/action-gh-release@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
build-release / release-pypi / release
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/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
build-release / docs-release / build-deploy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, conda-incubator/setup-miniconda@v3, peaceiris/actions-gh-pages@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
build-release / docs-release / build-deploy
`auto-activate-base` is deprecated. Please use `auto-activate`. If your installer does not use the `base` environment as the default environment, also add `activate-environment: base`.
build-release / docs-release / build-deploy
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
build-release / docs-release / build-deploy
`auto-activate-base` is deprecated. Please use `auto-activate`. If your installer does not use the `base` environment as the default environment, also add `activate-environment: base`.

Artifacts

Produced during runtime
Name Size Digest
sdist
147 KB
sha256:bddc3033e375fa3c7ce06c3806bb23425f87e88fde535268ce67a3e94b69a8b1
wheel
16.3 KB
sha256:edb7f6fc6d90b92f794b5e2ff3283f541156b6004c31d6ec81ec8a86fa6fdced