[instructions] Sync instruction files with release v0.78.1 (#36600) #49132
pelikhanci.yml
on: push
changes
15s
js-integration-live-api
54s
audit
34s
health-smoke-copilot
31s
Integration Add Workflows
2m 27s
Integration Compile gh-aw-marketplace
0s
Integration Update - Preserve Local Imports
48s
Integration Update - Target Repo
57s
Integration Unauthenticated Add (Public Repo)
1m 3s
Integration Add with dispatch-workflow Dependencies
1m 16s
Integration Release Availability
14s
DIFC Proxy sh Integration Test
15s
GH_HOST Proxy PR Checkout Repro (Issue
11s
Matrix: integration
Matrix: windows-redirect-tests
Compile pkg/cli/workflows
14s
Annotations
29 errors, 36 warnings, and 1 notice
|
Integration: Parser Remote Fetch & Cache
Coverage upload failed (HTTP 403): Code quality is not enabled for this repository. Enable code quality in your repository settings.. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
|
|
Integration: CMD Tests
Coverage upload failed (HTTP 403): Code quality is not enabled for this repository. Enable code quality in your repository settings.. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
|
|
Integration: Workflow Tools & MCP
Coverage upload failed (HTTP 403): Code quality is not enabled for this repository. Enable code quality in your repository settings.. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
|
|
Integration: CLI Safe Update
Coverage upload failed (HTTP 403): Code quality is not enabled for this repository. Enable code quality in your repository settings.. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
|
|
Integration: CLI MCP Inspect GitHub
Coverage upload failed (HTTP 403): Code quality is not enabled for this repository. Enable code quality in your repository settings.. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
|
|
Integration: Parser Location & Validation
Coverage upload failed (HTTP 403): Code quality is not enabled for this repository. Enable code quality in your repository settings.. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
|
|
Integration: CLI Security Tools
Coverage upload failed (HTTP 403): Code quality is not enabled for this repository. Enable code quality in your repository settings.. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
|
|
Redirect Resolution Tests (ubuntu-latest)
Coverage upload failed (HTTP 403): Code quality is not enabled for this repository. Enable code quality in your repository settings.. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
|
|
Integration: CLI Compile Workflows
Coverage upload failed (HTTP 403): Code quality is not enabled for this repository. Enable code quality in your repository settings.. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
|
|
Integration: Workflow Infra
Coverage upload failed (HTTP 403): Code quality is not enabled for this repository. Enable code quality in your repository settings.. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
|
|
Integration: CLI Update Command
Coverage upload failed (HTTP 403): Code quality is not enabled for this repository. Enable code quality in your repository settings.. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
|
|
Integration: Workflow Compiler
Coverage upload failed (HTTP 403): Code quality is not enabled for this repository. Enable code quality in your repository settings.. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
|
|
Integration: CLI MCP Other
Coverage upload failed (HTTP 403): Code quality is not enabled for this repository. Enable code quality in your repository settings.. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
|
|
Integration Unauthenticated Add (Public Repo)
Coverage upload failed (HTTP 403): Code quality is not enabled for this repository. Enable code quality in your repository settings.. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
|
|
Integration: CLI Audit Logs & Firewall
Coverage upload failed (HTTP 403): Code quality is not enabled for this repository. Enable code quality in your repository settings.. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
|
|
Integration: Workflow Validation
Coverage upload failed (HTTP 403): Code quality is not enabled for this repository. Enable code quality in your repository settings.. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
|
|
Integration: Workflow Features
Coverage upload failed (HTTP 403): Code quality is not enabled for this repository. Enable code quality in your repository settings.. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
|
|
Integration: Workflow Misc Part 2
Coverage upload failed (HTTP 403): Code quality is not enabled for this repository. Enable code quality in your repository settings.. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
|
|
Integration: Workflow Actions & Containers
Coverage upload failed (HTTP 403): Code quality is not enabled for this repository. Enable code quality in your repository settings.. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
|
|
Integration: CLI Compile & Poutine
Coverage upload failed (HTTP 403): Code quality is not enabled for this repository. Enable code quality in your repository settings.. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
|
|
Integration: Workflow Rendering & Bundling
Coverage upload failed (HTTP 403): Code quality is not enabled for this repository. Enable code quality in your repository settings.. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
|
|
Integration: CLI Completion & Other
Coverage upload failed (HTTP 403): Code quality is not enabled for this repository. Enable code quality in your repository settings.. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
|
|
Integration: CLI HTTP MCP Connect
Coverage upload failed (HTTP 403): Code quality is not enabled for this repository. Enable code quality in your repository settings.. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
|
|
Integration: CLI Add & List Commands
Coverage upload failed (HTTP 403): Code quality is not enabled for this repository. Enable code quality in your repository settings.. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
|
|
Integration Add with dispatch-workflow Dependencies
Coverage upload failed (HTTP 403): Code quality is not enabled for this repository. Enable code quality in your repository settings.. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
|
|
Integration: CLI Progress Flag
Coverage upload failed (HTTP 403): Code quality is not enabled for this repository. Enable code quality in your repository settings.. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
|
|
Integration: CLI Docker Build
Coverage upload failed (HTTP 403): Code quality is not enabled for this repository. Enable code quality in your repository settings.. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
|
|
Redirect Resolution Tests (windows-latest)
Coverage upload failed (HTTP 403): Code quality is not enabled for this repository. Enable code quality in your repository settings.. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
|
|
Integration: CLI MCP Connectivity
Coverage upload failed (HTTP 403): Code quality is not enabled for this repository. Enable code quality in your repository settings.. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
|
|
health-smoke-copilot
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
audit
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Integration: Parser Remote Fetch & Cache
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Integration: CMD Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Integration Update - Preserve Local Imports
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Integration: Workflow Tools & MCP
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Integration: CLI Safe Update
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Integration: CLI MCP Inspect GitHub
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Integration: Parser Location & Validation
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Integration: CLI Security Tools
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Integration Update - Target Repo
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Redirect Resolution Tests (ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Integration: CLI Compile Workflows
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Integration: Workflow Infra
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Integration: CLI Update Command
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Integration: Workflow Compiler
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Integration: CLI MCP Other
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Integration Unauthenticated Add (Public Repo)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Integration: CLI Audit Logs & Firewall
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Integration: Workflow Validation
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Integration: Workflow Features
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Integration: Workflow Misc Part 2
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Integration: Workflow Actions & Containers
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Integration: CLI Compile & Poutine
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Integration: Workflow Rendering & Bundling
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Integration: CLI Completion & Other
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Integration: CLI HTTP MCP Connect
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Integration: CLI Add & List Commands
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Integration Add with dispatch-workflow Dependencies
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Integration: CLI Progress Flag
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
update
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Integration: CLI Docker Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Redirect Resolution Tests (windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Integration: CLI MCP Connectivity
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Compile pkg/cli/workflows
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@fa0a91b85d4f404e444e00e005971372dc801d16. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Integration Add Workflows
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@4dc6199c7b1a012772edbd06daecab0f50c9053c. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Redirect Resolution Tests (windows-latest)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
dependency-audit
Expired
|
1.36 KB |
sha256:ec03f3959b8ceea550e273f0d3300173f5cbdf741b7c59b18755120bf050c4cb
|
|
|
gh-aw-linux-amd64
Expired
|
10.5 MB |
sha256:156b8e47d36293a9e62d71e86dac374048e0275c4e6fe9ddc3f84b77f933c28b
|
|
|
test-result-integration-CLI Add & List Commands
Expired
|
5.13 KB |
sha256:95b6d65bf5db7e6425f1979a372a38a0cb4b968c590d9c42df3cac8c27a9aa08
|
|
|
test-result-integration-CLI Audit Logs & Firewall
Expired
|
1.42 KB |
sha256:ba2b8415918c4036bb29a94f1c7939d01d8909c64843d3b3b00cb38cb5c094f0
|
|
|
test-result-integration-CLI Compile & Poutine
Expired
|
4.96 KB |
sha256:167651617b002bea9dc60d1c01b05a8c35a547509ac4b7fa65a0ed15df0ae3c4
|
|
|
test-result-integration-CLI Compile Workflows
Expired
|
8.48 KB |
sha256:6aaa73b78b9fc4d19f75fd73f97ca763f2abefcda52f3b25851e548e9e2cb6ac
|
|
|
test-result-integration-CLI Completion & Other
Expired
|
88.1 KB |
sha256:136809d56fdf1f66f06af6aabacce0fb4beef08c7374e2d2ecbf8975a61a8ff3
|
|
|
test-result-integration-CLI Docker Build
Expired
|
1.09 KB |
sha256:71033520391475698da3cb5db4683101b63ad5e594be2a711902dcaec0860da2
|
|
|
test-result-integration-CLI HTTP MCP Connect
Expired
|
739 Bytes |
sha256:074d7debc8e451bd32f3ea1c22d68d6bcfab9f13df7a503cb70c1c0df460bce9
|
|
|
test-result-integration-CLI MCP Connectivity
Expired
|
2.56 KB |
sha256:db49a4cdf1d0771d318782c995332d92618da23c74189a1bd83e4bb2650d7681
|
|
|
test-result-integration-CLI MCP Inspect GitHub
Expired
|
7.46 KB |
sha256:9a8486967bd05ea82eef44386c8be2777394801a0154b6139c6e7c613af29c0d
|
|
|
test-result-integration-CLI MCP Other
Expired
|
16.6 KB |
sha256:fa7cb131eabdd0c24ca2188b6450fa82aac91a462e92de373014fc4e843252b2
|
|
|
test-result-integration-CLI Progress Flag
Expired
|
531 Bytes |
sha256:7a33abfe21cb7a5861614af7057725928f612a6b8f2b8d5dc32e22063f8d632c
|
|
|
test-result-integration-CLI Safe Update
Expired
|
4.4 KB |
sha256:843f9c3e1be36382f24a3e6f4abd7f20665f5b165dbab9c419770b06d7f4cc5a
|
|
|
test-result-integration-CLI Security Tools
Expired
|
1.54 KB |
sha256:5cbf67549d1a6976445cf986867a6593cd7ca96ecb6b6aa29dfd287994e77d41
|
|
|
test-result-integration-CLI Update Command
Expired
|
1.99 KB |
sha256:49b10ead45b914d5853b8f46dfeb9ff91ea3fe9ea290a1a75fa8568c627c2381
|
|
|
test-result-integration-CMD Tests
Expired
|
7.02 KB |
sha256:f9decdd572f0a0c5f725c212bf6a7348cf12c59a6b9ec638466a1f5fc89ce073
|
|
|
test-result-integration-Parser Location & Validation
Expired
|
2.79 KB |
sha256:04a785fd2f9411620d106f100bfc7ff0045307777012b47feb4bec99ba3b5b16
|
|
|
test-result-integration-Parser Remote Fetch & Cache
Expired
|
1.4 KB |
sha256:2eec6c3420ca6aeb418161857a2729a953480320977799d1a03b0069a156ea31
|
|
|
test-result-integration-Workflow Actions & Containers
Expired
|
5.15 KB |
sha256:7ac4d53aeeb9cb81ff6c94a5b19c22f8199680e38d30979088497f5436d0b5f1
|
|
|
test-result-integration-Workflow Compiler
Expired
|
8.29 KB |
sha256:9a763e340ee627c9eb3d49237a8c4eb0d5cab7b139de5da0046967e80e93fd2d
|
|
|
test-result-integration-Workflow Features
Expired
|
41.2 KB |
sha256:dbab0dd8688d120929181f02f2e66b5a11ea1964e8606c0112d6bca868b4ac77
|
|
|
test-result-integration-Workflow Infra
Expired
|
24.6 KB |
sha256:1ddcb5be8bbbf5fffcd8095a4439b1b00a25b095bab2e339fa1748aecdfd50ef
|
|
|
test-result-integration-Workflow Misc Part 2
Expired
|
68.4 KB |
sha256:486221479c39b230f01a8639695996e318bb4165bb215b72feb2edd696901b75
|
|
|
test-result-integration-Workflow Rendering & Bundling
Expired
|
24.7 KB |
sha256:76e4160df25b9e15d5d7c6824f59364f6becdb6f3a0a0a43d9840a5ed2a4e222
|
|
|
test-result-integration-Workflow Tools & MCP
Expired
|
8.61 KB |
sha256:e62ce5697a3dc62f5309d61eddda432b6f342399458e9688d7421af02d5dc603
|
|
|
test-result-integration-Workflow Validation
Expired
|
3.31 KB |
sha256:fe27b38ba0ab9307d1fa50e2beaf8f07053fa6ea636c02fd43ed771ac822b1d2
|
|
|
test-result-integration-add-dispatch-workflow
Expired
|
2.58 KB |
sha256:4d518bc072ce693fa1c9b8ab626c504c08ee9ebc5aeb23e02f1b48a26bb46665
|
|
|
test-result-integration-unauthenticated
Expired
|
1.56 KB |
sha256:babac7709a40877f5f753049f611bc7eef552c0e30db8ebfc6fb663ac4f1f51a
|
|