Skip to content

CHORE: Bump the development-dependencies group across 1 directory with 11 updates #2267

CHORE: Bump the development-dependencies group across 1 directory with 11 updates

CHORE: Bump the development-dependencies group across 1 directory with 11 updates #2267

Triggered via pull request March 27, 2026 21:42
Status Failure
Total duration 1m 18s
Artifacts

label.yml

on: pull_request
Set labels
4s
Set labels
Create changelog fragment
39s
Create changelog fragment
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 2 warnings
Create changelog fragment
The process '/usr/bin/git' failed with exit code 128
Create changelog fragment
could not read Username for 'https://github.com': terminal prompts disabled
Create changelog fragment
could not read Username for 'https://github.com': terminal prompts disabled
Create changelog fragment
could not read Username for 'https://github.com': terminal prompts disabled
Syncer
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/
Set labels
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/labeler@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/