Skip to content

safe.bareRepository: default to "explicit" with WITH_BREAKING_CHANGES #27160

safe.bareRepository: default to "explicit" with WITH_BREAKING_CHANGES

safe.bareRepository: default to "explicit" with WITH_BREAKING_CHANGES #27160

Triggered via pull request April 1, 2026 08:28
Status Failure
Total duration 34m 23s
Artifacts 17

main.yml

on: pull_request
win+VS build
0s
win+VS build
win+Meson build
3m 59s
win+Meson build
Matrix: dockerized
Matrix: regular
Matrix: win+VS test
Matrix: win+Meson test
Matrix: win test
Fit to window
Zoom out
Zoom in

Annotations

154 errors and 74 warnings
linux-musl-meson (alpine:latest)
Process completed with exit code 1.
linux-musl-meson (alpine:latest)
Process completed with exit code 1.
linux-musl-meson (alpine:latest)
failed: t5541.12 non-fast-forward push show ref status
linux-musl-meson (alpine:latest)
failed: t5541.11 non-fast-forward push fails
linux-musl-meson (alpine:latest)
failed: t5541.10 rejected update prints status
linux-musl-meson (alpine:latest)
failed: t5541.8 create and delete remote branch
linux-musl-meson (alpine:latest)
failed: t5541.7 push already up-to-date
linux-musl-meson (alpine:latest)
failed: t5541.6 push to remote repository (standard) with sending Accept-Language
linux-musl-meson (alpine:latest)
failed: t5541.5 used receive-pack service
linux-musl-meson (alpine:latest)
failed: t5541.4 push to remote repository (standard)
linux-musl-meson (alpine:latest)
failed: t5541.3 clone remote repository
linux32 (i386/ubuntu:focal)
Process completed with exit code 2.
linux32 (i386/ubuntu:focal)
failed: t5540.15 non-fast-forward push show ref status
linux32 (i386/ubuntu:focal)
failed: t5540.14 non-fast-forward push fails
linux32 (i386/ubuntu:focal)
failed: t5540.13 PUT and MOVE sends object to URLs with SHA-1 hash suffix
linux32 (i386/ubuntu:focal)
failed: t5540.11 non-force push fails if not up to date
linux32 (i386/ubuntu:focal)
failed: t5540.10 create and delete remote branch
linux32 (i386/ubuntu:focal)
failed: t5540.9 http-push fetches packed objects
linux32 (i386/ubuntu:focal)
failed: t5540.8 http-push fetches unpacked objects
linux32 (i386/ubuntu:focal)
failed: t5540.7 push to remote repository with unpacked refs
linux32 (i386/ubuntu:focal)
failed: t5540.6 push already up-to-date
linux32 (i386/ubuntu:focal)
failed: t5540.5 push to remote repository with packed refs
linux-breaking-changes (ubuntu:rolling)
failed: t5540.13 PUT and MOVE sends object to URLs with SHA-1 hash suffix
linux-breaking-changes (ubuntu:rolling)
failed: t5540.11 non-force push fails if not up to date
linux-breaking-changes (ubuntu:rolling)
failed: t5540.10 create and delete remote branch
linux-breaking-changes (ubuntu:rolling)
failed: t5540.9 http-push fetches packed objects
linux-breaking-changes (ubuntu:rolling)
failed: t5540.8 http-push fetches unpacked objects
linux-breaking-changes (ubuntu:rolling)
failed: t5540.7 push to remote repository with unpacked refs
linux-breaking-changes (ubuntu:rolling)
failed: t5540.6 push already up-to-date
linux-breaking-changes (ubuntu:rolling)
failed: t5540.5 push to remote repository with packed refs
linux-breaking-changes (ubuntu:rolling)
failed: t5003.82 archive remote http repository
linux-breaking-changes (ubuntu:rolling)
failed: t5003.79 setup for HTTP protocol
linux-TEST-vars (ubuntu:20.04)
Process completed with exit code 2.
linux-TEST-vars (ubuntu:20.04)
failed: t5540.15 non-fast-forward push show ref status
linux-TEST-vars (ubuntu:20.04)
failed: t5540.14 non-fast-forward push fails
linux-TEST-vars (ubuntu:20.04)
failed: t5540.13 PUT and MOVE sends object to URLs with SHA-1 hash suffix
linux-TEST-vars (ubuntu:20.04)
failed: t5540.11 non-force push fails if not up to date
linux-TEST-vars (ubuntu:20.04)
failed: t5540.10 create and delete remote branch
linux-TEST-vars (ubuntu:20.04)
failed: t5540.9 http-push fetches packed objects
linux-TEST-vars (ubuntu:20.04)
failed: t5540.8 http-push fetches unpacked objects
linux-TEST-vars (ubuntu:20.04)
failed: t5540.7 push to remote repository with unpacked refs
linux-TEST-vars (ubuntu:20.04)
failed: t5540.6 push already up-to-date
linux-TEST-vars (ubuntu:20.04)
failed: t5540.5 push to remote repository with packed refs
linux-reftable (ubuntu:rolling)
Process completed with exit code 1.
linux-reftable (ubuntu:rolling)
failed: t5541.12 non-fast-forward push show ref status
linux-reftable (ubuntu:rolling)
failed: t5541.11 non-fast-forward push fails
linux-reftable (ubuntu:rolling)
failed: t5541.10 rejected update prints status
linux-reftable (ubuntu:rolling)
failed: t5541.8 create and delete remote branch
linux-reftable (ubuntu:rolling)
failed: t5541.7 push already up-to-date
linux-reftable (ubuntu:rolling)
failed: t5541.6 push to remote repository (standard) with sending Accept-Language
linux-reftable (ubuntu:rolling)
failed: t5541.5 used receive-pack service
linux-reftable (ubuntu:rolling)
failed: t5541.4 push to remote repository (standard)
linux-reftable (ubuntu:rolling)
failed: t5541.3 clone remote repository
debian-11 (debian:11)
Process completed with exit code 2.
debian-11 (debian:11)
failed: t5540.15 non-fast-forward push show ref status
debian-11 (debian:11)
failed: t5540.14 non-fast-forward push fails
debian-11 (debian:11)
failed: t5540.13 PUT and MOVE sends object to URLs with SHA-1 hash suffix
debian-11 (debian:11)
failed: t5540.11 non-force push fails if not up to date
debian-11 (debian:11)
failed: t5540.10 create and delete remote branch
debian-11 (debian:11)
failed: t5540.9 http-push fetches packed objects
debian-11 (debian:11)
failed: t5540.8 http-push fetches unpacked objects
debian-11 (debian:11)
failed: t5540.7 push to remote repository with unpacked refs
debian-11 (debian:11)
failed: t5540.6 push already up-to-date
debian-11 (debian:11)
failed: t5540.5 push to remote repository with packed refs
linux-meson (ubuntu:rolling)
failed: t5540.15 non-fast-forward push show ref status
linux-meson (ubuntu:rolling)
failed: t5540.14 non-fast-forward push fails
linux-meson (ubuntu:rolling)
failed: t5540.13 PUT and MOVE sends object to URLs with SHA-1 hash suffix
linux-meson (ubuntu:rolling)
failed: t5540.11 non-force push fails if not up to date
linux-meson (ubuntu:rolling)
failed: t5540.10 create and delete remote branch
linux-meson (ubuntu:rolling)
failed: t5540.9 http-push fetches packed objects
linux-meson (ubuntu:rolling)
failed: t5540.8 http-push fetches unpacked objects
linux-meson (ubuntu:rolling)
failed: t5540.7 push to remote repository with unpacked refs
linux-meson (ubuntu:rolling)
failed: t5540.6 push already up-to-date
linux-meson (ubuntu:rolling)
failed: t5540.5 push to remote repository with packed refs
linux-sha256 (ubuntu:rolling)
failed: t5540.15 non-fast-forward push show ref status
linux-sha256 (ubuntu:rolling)
failed: t5540.14 non-fast-forward push fails
linux-sha256 (ubuntu:rolling)
failed: t5540.13 PUT and MOVE sends object to URLs with SHA-1 hash suffix
linux-sha256 (ubuntu:rolling)
failed: t5540.11 non-force push fails if not up to date
linux-sha256 (ubuntu:rolling)
failed: t5540.10 create and delete remote branch
linux-sha256 (ubuntu:rolling)
failed: t5540.9 http-push fetches packed objects
linux-sha256 (ubuntu:rolling)
failed: t5540.8 http-push fetches unpacked objects
linux-sha256 (ubuntu:rolling)
failed: t5540.7 push to remote repository with unpacked refs
linux-sha256 (ubuntu:rolling)
failed: t5540.6 push already up-to-date
linux-sha256 (ubuntu:rolling)
failed: t5540.5 push to remote repository with packed refs
osx-clang (macos-14)
failed: t5540.15 non-fast-forward push show ref status
osx-clang (macos-14)
failed: t5540.14 non-fast-forward push fails
osx-clang (macos-14)
failed: t5540.13 PUT and MOVE sends object to URLs with SHA-1 hash suffix
osx-clang (macos-14)
failed: t5540.11 non-force push fails if not up to date
osx-clang (macos-14)
failed: t5540.10 create and delete remote branch
osx-clang (macos-14)
failed: t5540.9 http-push fetches packed objects
osx-clang (macos-14)
failed: t5540.8 http-push fetches unpacked objects
osx-clang (macos-14)
failed: t5540.7 push to remote repository with unpacked refs
osx-clang (macos-14)
failed: t5540.6 push already up-to-date
osx-clang (macos-14)
failed: t5540.5 push to remote repository with packed refs
osx-reftable (macos-14)
Process completed with exit code 1.
osx-reftable (macos-14)
failed: t5541.12 non-fast-forward push show ref status
osx-reftable (macos-14)
failed: t5541.11 non-fast-forward push fails
osx-reftable (macos-14)
failed: t5541.10 rejected update prints status
osx-reftable (macos-14)
failed: t5541.8 create and delete remote branch
osx-reftable (macos-14)
failed: t5541.7 push already up-to-date
osx-reftable (macos-14)
failed: t5541.6 push to remote repository (standard) with sending Accept-Language
osx-reftable (macos-14)
failed: t5541.5 used receive-pack service
osx-reftable (macos-14)
failed: t5541.4 push to remote repository (standard)
osx-reftable (macos-14)
failed: t5541.3 clone remote repository
osx-gcc (macos-14)
failed: t5540.15 non-fast-forward push show ref status
osx-gcc (macos-14)
failed: t5540.14 non-fast-forward push fails
osx-gcc (macos-14)
failed: t5540.13 PUT and MOVE sends object to URLs with SHA-1 hash suffix
osx-gcc (macos-14)
failed: t5540.11 non-force push fails if not up to date
osx-gcc (macos-14)
failed: t5540.10 create and delete remote branch
osx-gcc (macos-14)
failed: t5540.9 http-push fetches packed objects
osx-gcc (macos-14)
failed: t5540.8 http-push fetches unpacked objects
osx-gcc (macos-14)
failed: t5540.7 push to remote repository with unpacked refs
osx-gcc (macos-14)
failed: t5540.6 push already up-to-date
osx-gcc (macos-14)
failed: t5540.5 push to remote repository with packed refs
osx-meson (macos-14)
failed: t5540.15 non-fast-forward push show ref status
osx-meson (macos-14)
failed: t5540.14 non-fast-forward push fails
osx-meson (macos-14)
failed: t5540.13 PUT and MOVE sends object to URLs with SHA-1 hash suffix
osx-meson (macos-14)
failed: t5540.11 non-force push fails if not up to date
osx-meson (macos-14)
failed: t5540.10 create and delete remote branch
osx-meson (macos-14)
failed: t5540.9 http-push fetches packed objects
osx-meson (macos-14)
failed: t5540.8 http-push fetches unpacked objects
osx-meson (macos-14)
failed: t5540.7 push to remote repository with unpacked refs
osx-meson (macos-14)
failed: t5540.6 push already up-to-date
osx-meson (macos-14)
failed: t5540.5 push to remote repository with packed refs
linux-leaks (ubuntu:rolling)
failed: t5540.15 non-fast-forward push show ref status
linux-leaks (ubuntu:rolling)
failed: t5540.14 non-fast-forward push fails
linux-leaks (ubuntu:rolling)
failed: t5540.13 PUT and MOVE sends object to URLs with SHA-1 hash suffix
linux-leaks (ubuntu:rolling)
failed: t5540.11 non-force push fails if not up to date
linux-leaks (ubuntu:rolling)
failed: t5540.10 create and delete remote branch
linux-leaks (ubuntu:rolling)
failed: t5540.9 http-push fetches packed objects
linux-leaks (ubuntu:rolling)
failed: t5540.8 http-push fetches unpacked objects
linux-leaks (ubuntu:rolling)
failed: t5540.7 push to remote repository with unpacked refs
linux-leaks (ubuntu:rolling)
failed: t5540.6 push already up-to-date
linux-leaks (ubuntu:rolling)
failed: t5540.5 push to remote repository with packed refs
linux-reftable-leaks (ubuntu:rolling)
Process completed with exit code 1.
linux-reftable-leaks (ubuntu:rolling)
failed: t5541.12 non-fast-forward push show ref status
linux-reftable-leaks (ubuntu:rolling)
failed: t5541.11 non-fast-forward push fails
linux-reftable-leaks (ubuntu:rolling)
failed: t5541.10 rejected update prints status
linux-reftable-leaks (ubuntu:rolling)
failed: t5541.8 create and delete remote branch
linux-reftable-leaks (ubuntu:rolling)
failed: t5541.7 push already up-to-date
linux-reftable-leaks (ubuntu:rolling)
failed: t5541.6 push to remote repository (standard) with sending Accept-Language
linux-reftable-leaks (ubuntu:rolling)
failed: t5541.5 used receive-pack service
linux-reftable-leaks (ubuntu:rolling)
failed: t5541.4 push to remote repository (standard)
linux-reftable-leaks (ubuntu:rolling)
failed: t5541.3 clone remote repository
linux-asan-ubsan (ubuntu:rolling)
failed: t5540.15 non-fast-forward push show ref status
linux-asan-ubsan (ubuntu:rolling)
failed: t5540.14 non-fast-forward push fails
linux-asan-ubsan (ubuntu:rolling)
failed: t5540.13 PUT and MOVE sends object to URLs with SHA-1 hash suffix
linux-asan-ubsan (ubuntu:rolling)
failed: t5540.11 non-force push fails if not up to date
linux-asan-ubsan (ubuntu:rolling)
failed: t5540.10 create and delete remote branch
linux-asan-ubsan (ubuntu:rolling)
failed: t5540.9 http-push fetches packed objects
linux-asan-ubsan (ubuntu:rolling)
failed: t5540.8 http-push fetches unpacked objects
linux-asan-ubsan (ubuntu:rolling)
failed: t5540.7 push to remote repository with unpacked refs
linux-asan-ubsan (ubuntu:rolling)
failed: t5540.6 push already up-to-date
linux-asan-ubsan (ubuntu:rolling)
failed: t5540.5 push to remote repository with packed refs
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/
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. 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/
win+Meson build
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
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. 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-musl-meson (alpine: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/
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)
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
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
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)
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-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-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-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/
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)
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-meson (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)
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/
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. 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/
win+Meson test (7)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
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. 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/
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 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/
win+Meson test (3)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
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)
JGit wasn't installed, see above for clues why
osx-clang (macos-14)
Already linked: /opt/homebrew/Cellar/gettext/1.0
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. 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/
win+Meson test (6)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
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)
JGit wasn't installed, see above for clues why
osx-reftable (macos-14)
Already linked: /opt/homebrew/Cellar/gettext/1.0
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. 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/
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. 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/
win+Meson test (0)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
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, 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. 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/
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. 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/
win+Meson test (8)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
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)
JGit wasn't installed, see above for clues why
osx-gcc (macos-14)
Already linked: /opt/homebrew/Cellar/gettext/1.0
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. 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/
win+Meson test (5)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
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, 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. 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/
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. 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/
win+Meson test (2)
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. 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/
win+Meson test (1)
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
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, 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. 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/
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, 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. 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/
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, 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. 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/
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, 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. 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/
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, 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. 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/
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, 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. 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/
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, 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. 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)
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)
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/
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, 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. 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)
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/

Artifacts

Produced during runtime
Name Size Digest
failed-tests-debian-11
161 KB
sha256:6081517950241d2cb46b2f5efea7ce0ad5cfa8bb20af353e1ee8009279ed2341
failed-tests-linux-TEST-vars
168 KB
sha256:829ee7a4a0c03f6bc3cc3faa6a1927a8575a4b2484b655b012b941d32bf82e2a
failed-tests-linux-asan-ubsan
161 KB
sha256:36490dec3c918d729dfe2d41c94a474870a9a8dfbfa398688849efc1c7fccb3d
failed-tests-linux-breaking-changes
1.97 MB
sha256:27189d793573e802a911e1720d669520b02f78bbb7d50add70eef83512891535
failed-tests-linux-leaks
161 KB
sha256:0c22ed506b2ac5aec44eb10a309795aec7d0c1f058f336b9e895005eb7a08215
failed-tests-linux-meson
159 KB
sha256:b34af3d50831dc8ef7e5a316dbc750ed6cd1b9a1798b27cc9dcdd8d16ebda5fe
failed-tests-linux-musl-meson
43.8 KB
sha256:0dcac5b95266e33e7f255a95cd54fec43a4b3948c116e6e9675d68c8a59e6267
failed-tests-linux-reftable
45.3 KB
sha256:e000e4d60620ed31aab7d361c95cb0fcb64577f1d14a35df36130c4b21331912
failed-tests-linux-reftable-leaks
45.3 KB
sha256:086eb7bb45960030c50a95acba422eaefde4e1d1df3b380a42e493c9214c68d4
failed-tests-linux-sha256
162 KB
sha256:8fcd112dd5c5b8155fb985e34b3808b5e8515ccc8f3d11425962e89364d7a60a
failed-tests-linux32
162 KB
sha256:b1453bac713922d7c65907a6cfe59d2c19c41aacb1ba00933ad285374a662ae4
failed-tests-osx-clang
164 KB
sha256:8aa2a520af1e5b9406df4b8aef4c53b0771f5ba375eebe1eec7e08c6fffc1c90
failed-tests-osx-gcc
164 KB
sha256:56896fe57cc738ec96786da8209d89371081bfd2be997c3562e3d39964090fbb
failed-tests-osx-meson
168 KB
sha256:d51154cbb22d800e6621a61840ed15d63eb7ed1b45d27147ddb20d4c5a08cc03
failed-tests-osx-reftable
47.4 KB
sha256:1c7947fe48cf9deb7b04546930537ef493b122b05fdd7603ca40f4934b7fe672
windows-artifacts
96.5 MB
sha256:0bbdbf4bad7c126d7b50fadab7adbef65b722ba33b3c1fb6e598e10bc2ce21c3
windows-meson-artifacts
57 MB
sha256:5015ec0a6b6d151fda3c0e0695a27edd2a8014ab536c5cf7828ad1ebe96b9f2f