Skip to content

Update Unit Tests (#68) #21

Update Unit Tests (#68)

Update Unit Tests (#68) #21

Triggered via push January 9, 2024 01:30
Status Success
Total duration 47s
Artifacts
build_and_publish_pypi  /  bump_version
6s
build_and_publish_pypi / bump_version
build_and_publish_pypi  /  update_changelog
0s
build_and_publish_pypi / update_changelog
build_and_publish_pypi  /  build_and_publish_pypi
26s
build_and_publish_pypi / build_and_publish_pypi
build_and_publish_pypi  /  tag_prerelease
3s
build_and_publish_pypi / tag_prerelease
Fit to window
Zoom out
Zoom in

Annotations

6 warnings and 1 notice
build_and_publish_pypi / bump_version
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build_and_publish_pypi / bump_version
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build_and_publish_pypi / tag_prerelease
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@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_and_publish_pypi / build_and_publish_pypi
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build_and_publish_pypi / build_and_publish_pypi
Input 'packages_dir' has been deprecated with message: The inputs have been normalized to use kebab-case. Use `packages-dir` instead.
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
build_and_publish_pypi / build_and_publish_pypi
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/