Skip to content

feat(cli): aggregate step authorization into top-level config field #5507

feat(cli): aggregate step authorization into top-level config field

feat(cli): aggregate step authorization into top-level config field #5507

Triggered via pull request April 9, 2026 16:04
Status Cancelled
Total duration 1m 8s
Artifacts

build.yml

on: pull_request
Matrix: test
release
release
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 2 warnings
test (18.x, ubuntu-latest)
Canceling since a higher priority waiting request for Build-release-17.4.0 exists
test (18.x, ubuntu-latest)
The operation was canceled.
test (20.x, ubuntu-latest)
Canceling since a higher priority waiting request for Build-release-17.4.0 exists
test (20.x, ubuntu-latest)
The operation was canceled.
Build
Canceling since a higher priority waiting request for Build-release-17.4.0 exists
test (18.x, ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@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/
test (20.x, ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@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/