safe.bareRepository: default to "explicit" with WITH_BREAKING_CHANGES #2135
dschomain.yml
on: push
config
10s
fuzz smoke test
1m 17s
static-analysis
5m 36s
rust-analysis
1m 40s
sparse
3m 27s
documentation
7m 41s
Matrix: dockerized
Matrix: regular
Matrix: win+VS test
Matrix: win+Meson test
Matrix: win test
Annotations
30 errors and 98 warnings
|
osx-reftable (macos-14)
Process completed with exit code 1.
|
|
osx-clang (macos-14)
Process completed with exit code 1.
|
|
debian-11 (debian:11)
Process completed with exit code 1.
|
|
linux-leaks (ubuntu:rolling)
Process completed with exit code 1.
|
|
linux-TEST-vars (ubuntu:20.04)
Process completed with exit code 1.
|
|
linux-sha256 (ubuntu:rolling)
Process completed with exit code 1.
|
|
linux-breaking-changes (ubuntu:rolling)
Process completed with exit code 1.
|
|
osx-gcc (macos-14)
Process completed with exit code 1.
|
|
linux32 (i386/ubuntu:focal)
Process completed with exit code 1.
|
|
linux-reftable (ubuntu:rolling)
Process completed with exit code 1.
|
|
linux-reftable-leaks (ubuntu:rolling)
Process completed with exit code 1.
|
|
linux-asan-ubsan (ubuntu:rolling)
Process completed with exit code 1.
|
|
almalinux-8 (almalinux:8)
Process completed with exit code 1.
|
|
win test (7)
Process completed with exit code 1.
|
|
win test (9)
Process completed with exit code 1.
|
|
win test (1)
Process completed with exit code 1.
|
|
win test (2)
Process completed with exit code 1.
|
|
win test (8)
Process completed with exit code 1.
|
|
win test (4)
Process completed with exit code 1.
|
|
win test (6)
Process completed with exit code 1.
|
|
win test (3)
Process completed with exit code 1.
|
|
win test (0)
Process completed with exit code 1.
|
|
win test (5)
Process completed with exit code 1.
|
|
fedora-breaking-changes-meson (fedora:latest)
Process completed with exit code 1.
|
|
fedora-breaking-changes-meson (fedora:latest)
Process completed with exit code 1.
|
|
fedora-breaking-changes-meson (fedora:latest)
failed: t1800.43 server hooks expect stdout redirected to stderr
|
|
win+Meson test (3)
Process completed with exit code 1.
|
|
win+Meson test (3)
failed: t1800.43 server hooks expect stdout redirected to stderr
|
|
osx-meson (macos-14)
Process completed with exit code 1.
|
|
osx-meson (macos-14)
failed: t1800.43 server hooks expect stdout redirected to stderr
|
|
osx-reftable (macos-14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. 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/
|
|
osx-reftable (macos-14)
No files were found with the provided path: /Users/runner/work/git/git/t/failed-test-artifacts. No artifacts will be uploaded.
|
|
osx-reftable (macos-14)
JGit wasn't installed, see above for clues why
|
|
osx-reftable (macos-14)
Already linked: /opt/homebrew/Cellar/gettext/1.0
|
|
osx-clang (macos-14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. 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/
|
|
osx-clang (macos-14)
No files were found with the provided path: /Users/runner/work/git/git/t/failed-test-artifacts. No artifacts will be uploaded.
|
|
osx-clang (macos-14)
JGit wasn't installed, see above for clues why
|
|
osx-clang (macos-14)
Already linked: /opt/homebrew/Cellar/gettext/1.0
|
|
rust-analysis
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/
|
|
debian-11 (debian:11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. 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/
|
|
debian-11 (debian:11)
No files were found with the provided path: t/failed-test-artifacts. No artifacts will be uploaded.
|
|
debian-11 (debian:11)
JGit wasn't installed, see above for clues why
|
|
debian-11 (debian:11)
git-lfs wasn't installed, see above for clues why
|
|
debian-11 (debian:11)
perforce wasn't installed, see above for clues why
|
|
linux-leaks (ubuntu:rolling)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. 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/
|
|
linux-leaks (ubuntu:rolling)
No files were found with the provided path: t/failed-test-artifacts. No artifacts will be uploaded.
|
|
linux-TEST-vars (ubuntu:20.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. 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/
|
|
linux-TEST-vars (ubuntu:20.04)
No files were found with the provided path: t/failed-test-artifacts. No artifacts will be uploaded.
|
|
linux-sha256 (ubuntu:rolling)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. 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/
|
|
linux-sha256 (ubuntu:rolling)
No files were found with the provided path: t/failed-test-artifacts. No artifacts will be uploaded.
|
|
linux-breaking-changes (ubuntu:rolling)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. 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/
|
|
linux-breaking-changes (ubuntu:rolling)
No files were found with the provided path: t/failed-test-artifacts. No artifacts will be uploaded.
|
|
osx-gcc (macos-14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. 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/
|
|
osx-gcc (macos-14)
No files were found with the provided path: /Users/runner/work/git/git/t/failed-test-artifacts. No artifacts will be uploaded.
|
|
osx-gcc (macos-14)
JGit wasn't installed, see above for clues why
|
|
osx-gcc (macos-14)
Already linked: /opt/homebrew/Cellar/gettext/1.0
|
|
linux32 (i386/ubuntu:focal)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. 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/
|
|
linux32 (i386/ubuntu:focal)
No files were found with the provided path: t/failed-test-artifacts. No artifacts will be uploaded.
|
|
linux32 (i386/ubuntu:focal)
JGit wasn't installed, see above for clues why
|
|
linux32 (i386/ubuntu:focal)
git-lfs wasn't installed, see above for clues why
|
|
linux32 (i386/ubuntu:focal)
perforce wasn't installed, see above for clues why
|
|
linux-reftable (ubuntu:rolling)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. 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/
|
|
linux-reftable (ubuntu:rolling)
No files were found with the provided path: t/failed-test-artifacts. No artifacts will be uploaded.
|
|
linux-reftable-leaks (ubuntu:rolling)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. 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/
|
|
linux-reftable-leaks (ubuntu:rolling)
No files were found with the provided path: t/failed-test-artifacts. No artifacts will be uploaded.
|
|
linux-asan-ubsan (ubuntu:rolling)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. 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/
|
|
linux-asan-ubsan (ubuntu:rolling)
No files were found with the provided path: t/failed-test-artifacts. No artifacts will be uploaded.
|
|
almalinux-8 (almalinux:8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. 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/
|
|
almalinux-8 (almalinux:8)
No files were found with the provided path: t/failed-test-artifacts. No artifacts will be uploaded.
|
|
almalinux-8 (almalinux:8)
JGit wasn't installed, see above for clues why
|
|
almalinux-8 (almalinux:8)
git-lfs wasn't installed, see above for clues why
|
|
almalinux-8 (almalinux:8)
perforce wasn't installed, see above for clues why
|
|
win build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win test (7)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, actions/upload-artifact@v5, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win test (7)
No files were found with the provided path: t/failed-test-artifacts. No artifacts will be uploaded.
|
|
win test (9)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, actions/upload-artifact@v5, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win test (9)
No files were found with the provided path: t/failed-test-artifacts. No artifacts will be uploaded.
|
|
win test (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, actions/upload-artifact@v5, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win test (1)
No files were found with the provided path: t/failed-test-artifacts. No artifacts will be uploaded.
|
|
win test (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, actions/upload-artifact@v5, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win test (2)
No files were found with the provided path: t/failed-test-artifacts. No artifacts will be uploaded.
|
|
win test (8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, actions/upload-artifact@v5, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win test (8)
No files were found with the provided path: t/failed-test-artifacts. No artifacts will be uploaded.
|
|
win test (4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, actions/upload-artifact@v5, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win test (4)
No files were found with the provided path: t/failed-test-artifacts. No artifacts will be uploaded.
|
|
win test (6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, actions/upload-artifact@v5, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win test (6)
No files were found with the provided path: t/failed-test-artifacts. No artifacts will be uploaded.
|
|
win test (3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, actions/upload-artifact@v5, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win test (3)
No files were found with the provided path: t/failed-test-artifacts. No artifacts will be uploaded.
|
|
win test (0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, actions/upload-artifact@v5, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win test (0)
No files were found with the provided path: t/failed-test-artifacts. No artifacts will be uploaded.
|
|
win test (5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, actions/upload-artifact@v5, git-for-windows/setup-git-for-windows-sdk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win test (5)
No files were found with the provided path: t/failed-test-artifacts. No artifacts will be uploaded.
|
|
win+Meson build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win+Meson build
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
linux-musl-meson (alpine:latest)
JGit wasn't installed, see above for clues why
|
|
linux-musl-meson (alpine:latest)
git-lfs wasn't installed, see above for clues why
|
|
linux-musl-meson (alpine:latest)
perforce wasn't installed, see above for clues why
|
|
fedora-breaking-changes-meson (fedora:latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. 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/
|
|
fedora-breaking-changes-meson (fedora:latest)
JGit wasn't installed, see above for clues why
|
|
fedora-breaking-changes-meson (fedora:latest)
git-lfs wasn't installed, see above for clues why
|
|
fedora-breaking-changes-meson (fedora:latest)
perforce wasn't installed, see above for clues why
|
|
win+Meson test (9)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win+Meson test (9)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
win+Meson test (3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win+Meson test (3)
No files were found with the provided path: /d/a/git/git/build/test-output/failed-test-artifacts. No artifacts will be uploaded.
|
|
win+Meson test (3)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
win+Meson test (4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win+Meson test (4)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
win+Meson test (0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win+Meson test (0)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
win+Meson test (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win+Meson test (2)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
win+Meson test (5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win+Meson test (5)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
win+Meson test (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win+Meson test (1)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
win+Meson test (7)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win+Meson test (7)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
win+Meson test (8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win+Meson test (8)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
win+Meson test (6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
win+Meson test (6)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
osx-meson (macos-14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. 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/
|
|
osx-meson (macos-14)
JGit wasn't installed, see above for clues why
|
|
osx-meson (macos-14)
pcre2 10.47_1 is already installed and up-to-date.
To reinstall 10.47_1, run:
brew reinstall pcre2
|
|
osx-meson (macos-14)
ninja 1.13.2 is already installed and up-to-date.
To reinstall 1.13.2, run:
brew reinstall ninja
|
|
osx-meson (macos-14)
Already linked: /opt/homebrew/Cellar/gettext/1.0
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
failed-tests-fedora-breaking-changes-meson
|
45.4 KB |
sha256:a7431b5b658dcefac8b7322b55ed6acc81ce7d1d3e689977f3415a4eb995e785
|
|
|
failed-tests-osx-meson
|
46.9 KB |
sha256:43247c08e061906f7ec56fce5ed86d71a071ddff86865bfd6b09a5940cebbceb
|
|
|
windows-artifacts
|
96.8 MB |
sha256:ef266f891b63100f5175b68e89c4f46e918d72d54f936efec60b4472b5b428fc
|
|
|
windows-meson-artifacts
|
48.1 MB |
sha256:c95b2f21943496021683c1837dc161254ac2a3be49cc2c31ddadfe6fd9bbacd9
|
|