Skip to content

ci(mergify): upgrade configuration to current format #1340

ci(mergify): upgrade configuration to current format

ci(mergify): upgrade configuration to current format #1340

Triggered via push May 5, 2026 13:17
Status Failure
Total duration 1m 11s
Artifacts

python.yml

on: push
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

19 errors, 7 warnings, and 3 notices
build (3.7, macos-latest)
The version '3.7' with architecture 'arm64' was not found for macOS 15.7.4. The list of all available versions can be found here: https://raw.githubusercontent.com/actions/python-versions/main/versions-manifest.json
build (3.9, ubuntu-latest)
The strategy configuration was canceled because "build._3_7_macos-latest" failed
build (3.7, ubuntu-latest)
The strategy configuration was canceled because "build._3_7_macos-latest" failed
build (3.7, ubuntu-latest)
The version '3.7' with architecture 'x64' was not found for Ubuntu 24.04. The list of all available versions can be found here: https://raw.githubusercontent.com/actions/python-versions/main/versions-manifest.json
build (3.8, ubuntu-latest)
The strategy configuration was canceled because "build._3_7_macos-latest" failed
build (3.8, ubuntu-latest)
A task was canceled.
build (3.8, windows-latest)
The strategy configuration was canceled because "build._3_7_macos-latest" failed
build (3.8, windows-latest)
The operation was canceled.
build (3.7, windows-latest)
The strategy configuration was canceled because "build._3_7_macos-latest" failed
build (3.7, windows-latest)
The operation was canceled.
build (3.9, macos-latest)
The strategy configuration was canceled because "build._3_7_macos-latest" failed
build (3.9, macos-latest)
The operation was canceled.
build (3.9, macos-latest)
WARNING: Cache entry deserialization failed, entry ignored
build (3.9, windows-latest)
The strategy configuration was canceled because "build._3_7_macos-latest" failed
build (3.9, windows-latest)
The operation was canceled.
build (3.8, macos-latest)
The strategy configuration was canceled because "build._3_7_macos-latest" failed
build (3.8, macos-latest)
The operation was canceled.
build (3.8, macos-latest)
[notice] A new release of pip is available: 21.1.1 -> 25.0.1 [notice] To update, run: python3.8 -m pip install --upgrade pip
build (3.8, macos-latest)
WARNING: Cache entry deserialization failed, entry ignored
build (3.7, macos-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build (3.7, ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build (3.8, windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build (3.7, windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build (3.9, macos-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build (3.9, windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build (3.8, macos-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build (3.8, windows-latest)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
build (3.7, windows-latest)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
build (3.9, windows-latest)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026