Skip to content

QA tweaks

QA tweaks #70

Triggered via push September 24, 2024 21:24
Status Success
Total duration 2m 20s
Artifacts

ci.yml

on: push
unit-tests (3.10)
37s
unit-tests (3.10)
pre-commit
16s
pre-commit
Matrix: integration-tests
distribution
46s
distribution
Fit to window
Zoom out
Zoom in

Annotations

7 warnings
pre-commit
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
unit-tests (3.10)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, mamba-org/provision-with-micromamba@v14. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
integration-tests (3.10)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, mamba-org/provision-with-micromamba@v12. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
integration-tests (3.10)
The `save-state` 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/
distribution
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-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
Create a Trusted Publisher
A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):