Merge pull request #25 from stevenhua0320/fix-cli #6
sbillingebuild-wheel-release-upload.yml
on: push
build-release
/
...
/
check-tag
3s
build-release
/
...
/
check-privilege
3s
build-release
/
...
/
validate-pat-token
4s
build-release
/
...
/
validate-pypi-token
3s
build-release
/
...
/
get-python-versions
4s
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
/
...
/
release-update-changelog
6s
build-release
/
...
/
release-delete-create-new-tag
6s
build-release
/
...
/
get-python-versions
5s
build-release
/
...
/
release
19s
build-release
/
...
/
extract-latest
0s
build-release
/
...
/
build-deploy
0s
Annotations
1 error and 4 warnings
|
build-release / docs-release / get-python-version / get-python-versions / get-python-versions
The ref 'refs/tags/1.0.1' does not point to the expected commit '4ab4ca03e565ee2a3998fee35391edabd8061de2'. The ref may have been updated after the workflow was triggered.
|
|
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/setup-python@v4, 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/
|
|
build-release / release-github / release-update-changelog
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: stefanzweifel/git-auto-commit-action@v5. 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/
|
|
build-release / release-github / 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. 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/
|
|
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. 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
sdist
|
13.5 KB |
sha256:fa63b1e6005576e33566cc12d4cb1d84b041ade04bc14bf7ea684daa9e98c7e8
|
|
|
wheel
|
7.83 KB |
sha256:d96c0f0a26ff3ed3e6b82a70bf4d127d87e2d974b082df395a6512ab9661551a
|
|