Merge pull request #1929 from Bastian-Krause/bst/doc-conf-fixes #2449
push-pr-unit-tests.yml
on: push
Matrix: unit tests
Docker Unit Tests
/
docker
1m 22s
Release to Pypi
/
release
21s
Annotations
15 warnings
|
Docker Unit Tests / docker
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, docker/setup-compose-action@v1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
unit tests (3.11) / build
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, codecov/codecov-action@v4, codecov/test-results-action@v1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
unit tests (3.11) / build
This action is being deprecated in favor of 'codecov-action'.
Please update CI accordingly to use 'codecov-action@v5' with
'report_type: test_results'.
The 'codecov-action' should and can be run at least once for
coverage and once for test results
|
|
unit tests (3.10) / build
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, codecov/codecov-action@v4, codecov/test-results-action@v1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
unit tests (3.10) / build
This action is being deprecated in favor of 'codecov-action'.
Please update CI accordingly to use 'codecov-action@v5' with
'report_type: test_results'.
The 'codecov-action' should and can be run at least once for
coverage and once for test results
|
|
unit tests (3.14) / build
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, codecov/codecov-action@v4, codecov/test-results-action@v1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
unit tests (3.14) / build
This action is being deprecated in favor of 'codecov-action'.
Please update CI accordingly to use 'codecov-action@v5' with
'report_type: test_results'.
The 'codecov-action' should and can be run at least once for
coverage and once for test results
|
|
unit tests (3.12) / build
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, codecov/codecov-action@v4, codecov/test-results-action@v1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
unit tests (3.12) / build
This action is being deprecated in favor of 'codecov-action'.
Please update CI accordingly to use 'codecov-action@v5' with
'report_type: test_results'.
The 'codecov-action' should and can be run at least once for
coverage and once for test results
|
|
unit tests (3.13) / build
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5, codecov/codecov-action@v4, codecov/test-results-action@v1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
unit tests (3.13) / build
This action is being deprecated in favor of 'codecov-action'.
Please update CI accordingly to use 'codecov-action@v5' with
'report_type: test_results'.
The 'codecov-action' should and can be run at least once for
coverage and once for test results
|
|
Release to Pypi / release
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-python@v5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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):
|
|
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
|
|
attestations input ignored
The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.
|