バージョンを 2023.4.0.dev8 に上げる #320
miosakumabuild.yml
on: push
Matrix: build_linux_macos
Matrix: build_windows
create-release
48s
Matrix: publish_wheel
Annotations
16 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
|
|
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 (ubuntu-22.04_x86_64, 3.12)
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 (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.8)
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 (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.10)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|
|
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.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 (windows-2019, 3.11)
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.8)
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 (windows-2019, 3.12)
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 |
|