Skip to content
Python package

Merge branch 'release/1.3.2' #51

Sign in to view logs

Merge branch 'release/1.3.2'

Merge branch 'release/1.3.2' #51

Triggered via push December 25, 2023 11:17
@tanbrotanbro
pushed 36b6975
v1.3.2
Status Success
Total duration 1m 59s
Artifacts 1

python-package.yml

on: push
get-version-pep440
0s
get-version-pep440
Matrix: check
build
18s
build
publish
23s
publish
Fit to window
Zoom out
Zoom in

Annotations

8 warnings and 1 notice
check (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/
check (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/
check (3.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/
check (3.11)
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/
check (3.10)
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/
build
Cache paths are empty. Please check the previous logs and make sure that the python version is specified
build
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
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
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/

Artifacts

Produced during runtime
Name Size
pyyaml_include-dist-1.3.2 Expired
40.1 KB