Skip to content

[Java] Add class checker API (#890) #32

[Java] Add class checker API (#890)

[Java] Add class checker API (#890) #32

Triggered via push August 31, 2023 07:15
Status Success
Total duration 3m 12s
Artifacts

release.yaml

on: push
Matrix: Publish Python 📦 to PyPI
Fit to window
Zoom out
Zoom in

Annotations

10 warnings and 5 notices
Publish Python 📦 to PyPI (3.9)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
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 Python 📦 to PyPI (3.8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
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 Python 📦 to PyPI (3.6)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
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 Python 📦 to PyPI (3.10.12)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
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 Python 📦 to PyPI (3.7)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
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 Python 📦 to PyPI (3.9)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
Publish Python 📦 to PyPI (3.8)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
Publish Python 📦 to PyPI (3.6)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
Publish Python 📦 to PyPI (3.10.12)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
Publish Python 📦 to PyPI (3.7)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/