Skip to content

Fix build by pining pyyaml to 5.3.1 #234

Fix build by pining pyyaml to 5.3.1

Fix build by pining pyyaml to 5.3.1 #234

Triggered via pull request November 7, 2024 21:40
Status Failure
Total duration 4m 8s
Artifacts

python-package.yml

on: pull_request
code-quality
3s
code-quality
coverage
43s
coverage
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 4 warnings
code-quality
Process completed with exit code 2.
build (macos-latest, 3.8)
[notice] A new release of pip is available: 21.1.1 -> 24.3.1 [notice] To update, run: python3.8 -m pip install --upgrade pip
coverage
Your workflow is using a version of actions/cache that is scheduled for deprecation, actions/cache@v2. Please update your workflow to use the latest version of actions/cache to avoid interruptions. Learn more: https://github.blog/changelog/2024-09-16-notice-of-upcoming-deprecations-and-changes-in-github-actions-services/
code-quality
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
coverage
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
coverage
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/