Skip to content

バージョンを上げる #357

バージョンを上げる

バージョンを上げる #357

Triggered via push February 19, 2024 05:51
Status Success
Total duration 9m 35s
Artifacts 16

build.yml

on: push
Matrix: build_linux_macos
Matrix: build_windows
create-release
51s
create-release
Matrix: publish_wheel
Fit to window
Zoom out
Zoom in

Annotations

17 warnings and 16 notices
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
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
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
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
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
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
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
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
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
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
create-release
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: softprops/action-gh-release@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
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
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
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
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
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
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
publish_wheel (macos-13_arm64, 3.11)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
publish_wheel (macos-13_arm64, 3.10)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
publish_wheel (macos-13_arm64, 3.9)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
publish_wheel (windows-2019, 3.12)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
publish_wheel (ubuntu-22.04_x86_64, 3.9)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
publish_wheel (macos-13_arm64, 3.12)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
publish_wheel (windows-2019, 3.10)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
publish_wheel (ubuntu-22.04_x86_64, 3.8)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
publish_wheel (ubuntu-22.04_x86_64, 3.12)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
publish_wheel (ubuntu-20.04_armv8_jetson, 3.8)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
publish_wheel (ubuntu-22.04_x86_64, 3.11)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
publish_wheel (ubuntu-22.04_x86_64, 3.10)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
publish_wheel (windows-2019, 3.11)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
publish_wheel (windows-2019, 3.8)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
publish_wheel (windows-2019, 3.9)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
publish_wheel (macos-13_arm64, 3.8)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/

Artifacts

Produced during runtime
Name Size
macos-13_arm64_python-3.10 Expired
21.3 MB
macos-13_arm64_python-3.11 Expired
21.3 MB
macos-13_arm64_python-3.12 Expired
21.3 MB
macos-13_arm64_python-3.8 Expired
21.3 MB
macos-13_arm64_python-3.9 Expired
21.3 MB
ubuntu-20.04_armv8_jetson_python-3.8 Expired
11.4 MB
ubuntu-22.04_x86_64_python-3.10 Expired
25.9 MB
ubuntu-22.04_x86_64_python-3.11 Expired
25.9 MB
ubuntu-22.04_x86_64_python-3.12 Expired
25.9 MB
ubuntu-22.04_x86_64_python-3.8 Expired
25.9 MB
ubuntu-22.04_x86_64_python-3.9 Expired
25.9 MB
windows-2019_python-3.10 Expired
21.8 MB
windows-2019_python-3.11 Expired
21.8 MB
windows-2019_python-3.12 Expired
21.8 MB
windows-2019_python-3.8 Expired
21.8 MB
windows-2019_python-3.9 Expired
21.8 MB