Skip to content

Monitor component updates #8766

Monitor component updates

Monitor component updates #8766

Triggered via schedule March 17, 2026 09:09
Status Success
Total duration 17s
Artifacts

monitor-components.yml

on: schedule
Matrix: job
Fit to window
Zoom out
Zoom in

Annotations

29 warnings
job (msys2-runtime-package, https://github.com/msys2/MSYS2-packages/commits/master/msys2-runtime....
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: git-for-windows/rss-to-issues@v0. 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/
job (msys2-runtime-package, https://github.com/msys2/MSYS2-packages/commits/master/msys2-runtime....
Issue [New msys2-runtime-package version] msys2-runtime: Cygwin: Fix segfault when XSAVE area sizes are unalign… already exists
job (gnutls, https://gnutls.org/news.atom)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: git-for-windows/rss-to-issues@v0. 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/
job (tig, https://github.com/jonas/tig/tags.atom)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: git-for-windows/rss-to-issues@v0. 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/
job (cygwin, https://github.com/cygwin/cygwin/releases.atom, ^(?!.*newlib))
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: git-for-windows/rss-to-issues@v0. 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/
job (git, https://github.com/git/git/tags.atom)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: git-for-windows/rss-to-issues@v0. 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/
job (curl, https://github.com/curl/curl/tags.atom, ^(?!rc-))
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: git-for-windows/rss-to-issues@v0. 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/
job (curl, https://github.com/curl/curl/tags.atom, ^(?!rc-))
Issue [New curl version] 8.19.0 already exists
job (heimdal, https://github.com/heimdal/heimdal/tags.atom)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: git-for-windows/rss-to-issues@v0. 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/
job (libcbor, https://github.com/PJK/libcbor/tags.atom)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: git-for-windows/rss-to-issues@v0. 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/
job (pcre2, https://github.com/PCRE2Project/pcre2/tags.atom)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: git-for-windows/rss-to-issues@v0. 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/
job (innosetup, https://github.com/jrsoftware/issrc/tags.atom)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: git-for-windows/rss-to-issues@v0. 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/
job (innosetup, https://github.com/jrsoftware/issrc/tags.atom)
Issue [New innosetup version] Inno Setup 7.0.0-preview-2 already exists
job (7-zip, https://sourceforge.net/projects/sevenzip/rss?path=/7-Zip, true)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: git-for-windows/rss-to-issues@v0. 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/
job (git-lfs, https://github.com/git-lfs/git-lfs/tags.atom)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: git-for-windows/rss-to-issues@v0. 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/
job (msys2-runtime, https://github.com/msys2/msys2-runtime/commits/HEAD.atom, true)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: git-for-windows/rss-to-issues@v0. 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/
job (msys2-runtime, https://github.com/msys2/msys2-runtime/commits/HEAD.atom, true)
Issue [New msys2-runtime version] Cygwin: Fix segfault when XSAVE area sizes are unaligned already exists
job (perl, https://github.com/Perl/perl5/tags.atom, ^(?!.*(5\.[0-9]+[13579]|RC)))
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: git-for-windows/rss-to-issues@v0. 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/
job (libfido2, https://github.com/Yubico/libfido2/tags.atom)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: git-for-windows/rss-to-issues@v0. 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/
job (gitflow, https://github.com/petervanderdoes/gitflow-avh/tags.atom)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: git-for-windows/rss-to-issues@v0. 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/
job (git-credential-manager, https://github.com/git-ecosystem/git-credential-manager/tags.atom)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: git-for-windows/rss-to-issues@v0. 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/
job (git-credential-manager, https://github.com/git-ecosystem/git-credential-manager/tags.atom)
Issue [New git-credential-manager version] GCM 2.7.3 already exists
job (bash, https://git.savannah.gnu.org/cgit/bash.git/atom/?h=master, true)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: git-for-windows/rss-to-issues@v0. 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/
job (openssl, https://github.com/openssl/openssl/tags.atom, ^(?!.*alpha))
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: git-for-windows/rss-to-issues@v0. 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/
job (openssh, https://github.com/openssh/openssh-portable/tags.atom)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: git-for-windows/rss-to-issues@v0. 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/
job (mimalloc, https://github.com/microsoft/mimalloc/tags.atom, ^(?!v1\.|v3\.[01]\.))
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: git-for-windows/rss-to-issues@v0. 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/
job (git-sizer, https://github.com/github/git-sizer/tags.atom)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: git-for-windows/rss-to-issues@v0. 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/
job (mintty, https://github.com/mintty/mintty/releases.atom)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: git-for-windows/rss-to-issues@v0. 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/
job (mingw-w64-llvm, https://github.com/msys2/MINGW-packages/commits/master/mingw-w64-llvm.atom)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: git-for-windows/rss-to-issues@v0. 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/