Reduce Smoke CI REST churn by caching mention-resolution collaborator… #49252
pelikhanci.yml
on: push
changes
12s
js-integration-live-api
51s
audit
38s
health-smoke-copilot
38s
Integration Add Workflows
1m 6s
Integration Compile gh-aw-marketplace
0s
Integration Update - Preserve Local Imports
46s
Integration Update - Target Repo
56s
Integration Unauthenticated Add (Public Repo)
59s
Integration Add with dispatch-workflow Dependencies
57s
Integration Release Availability
14s
DIFC Proxy sh Integration Test
17s
GH_HOST Proxy PR Checkout Repro (Issue
22s
Matrix: integration
Matrix: windows-redirect-tests
Compile pkg/cli/workflows
0s
Annotations
72 errors, 36 warnings, and 1 notice
|
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: 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
Canceling since a higher priority waiting request for ci-refs/heads/main-integration-CLI Safe Update exists
|
|
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: Workflow Compiler
Canceling since a higher priority waiting request for ci-refs/heads/main-integration-Workflow Compiler exists
|
|
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 Update - Target Repo
Canceling since a higher priority waiting request for ci-refs/heads/main-integration-update-target-repo exists
|
|
Integration: Workflow Infra
Canceling since a higher priority waiting request for ci-refs/heads/main-integration-Workflow Infra exists
|
|
Integration: Workflow Infra
The operation was canceled.
|
|
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: Workflow Validation
Canceling since a higher priority waiting request for ci-refs/heads/main-integration-Workflow Validation exists
|
|
Integration: Workflow Validation
The operation was canceled.
|
|
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 Unauthenticated Add (Public Repo)
Canceling since a higher priority waiting request for ci-refs/heads/main-integration-unauthenticated-add exists
|
|
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
Canceling since a higher priority waiting request for ci-refs/heads/main-integration-CLI Audit Logs & Firewall exists
|
|
Integration Add with dispatch-workflow Dependencies
Canceling since a higher priority waiting request for ci-refs/heads/main-integration-add-dispatch-workflow exists
|
|
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 Add with dispatch-workflow Dependencies
The operation was canceled.
|
|
Integration: CLI Security Tools
Canceling since a higher priority waiting request for ci-refs/heads/main-integration-CLI Security Tools exists
|
|
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.
|
|
Integration: CLI Compile Workflows
Canceling since a higher priority waiting request for ci-refs/heads/main-integration-CLI Compile Workflows exists
|
|
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: CLI MCP Inspect GitHub
Canceling since a higher priority waiting request for ci-refs/heads/main-integration-CLI MCP Inspect GitHub exists
|
|
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: CLI Add & List Commands
Canceling since a higher priority waiting request for ci-refs/heads/main-integration-CLI Add & List Commands exists
|
|
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: CLI MCP Other
Canceling since a higher priority waiting request for ci-refs/heads/main-integration-CLI MCP Other exists
|
|
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.
|
|
Redirect Resolution Tests (windows-latest)
Canceling since a higher priority waiting request for ci-refs/heads/main-redirect-tests-windows-latest exists
|
|
Redirect Resolution Tests (windows-latest)
The operation was canceled.
|
|
Integration: CLI Update Command
Canceling since a higher priority waiting request for ci-refs/heads/main-integration-CLI Update Command exists
|
|
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: CLI Update Command
The operation was canceled.
|
|
Integration: CLI Compile & Poutine
Canceling since a higher priority waiting request for ci-refs/heads/main-integration-CLI Compile & Poutine exists
|
|
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: CLI Compile & Poutine
The operation was canceled.
|
|
Redirect Resolution Tests (ubuntu-latest)
Canceling since a higher priority waiting request for ci-refs/heads/main-redirect-tests-ubuntu-latest exists
|
|
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: Workflow Rendering & Bundling
Canceling since a higher priority waiting request for ci-refs/heads/main-integration-Workflow Rendering & Bundling exists
|
|
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: Workflow Rendering & Bundling
The operation was canceled.
|
|
Integration Add Workflows
Canceling since a higher priority waiting request for ci-refs/heads/main-integration-add exists
|
|
Integration Add Workflows
The operation was canceled.
|
|
Integration: Workflow Actions & Containers
Canceling since a higher priority waiting request for ci-refs/heads/main-integration-Workflow Actions & Containers exists
|
|
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: Workflow Actions & Containers
The operation was canceled.
|
|
Integration: Workflow Features
Canceling since a higher priority waiting request for ci-refs/heads/main-integration-Workflow Features exists
|
|
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 Features
The operation was canceled.
|
|
update
Canceling since a higher priority waiting request for ci-refs/heads/main-update exists
|
|
update
The operation was canceled.
|
|
Integration: CLI Progress Flag
Canceling since a higher priority waiting request for ci-refs/heads/main-integration-CLI Progress Flag exists
|
|
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 Progress Flag
The operation was canceled.
|
|
Integration: CLI HTTP MCP Connect
Canceling since a higher priority waiting request for ci-refs/heads/main-integration-CLI HTTP MCP Connect exists
|
|
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 HTTP MCP Connect
The operation was canceled.
|
|
Integration: CLI Completion & Other
Canceling since a higher priority waiting request for ci-refs/heads/main-integration-CLI Completion & Other exists
|
|
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 Completion & Other
The operation was canceled.
|
|
Integration: CLI MCP Connectivity
Canceling since a higher priority waiting request for ci-refs/heads/main-integration-CLI MCP Connectivity exists
|
|
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.
|
|
Integration: CLI MCP Connectivity
The operation was canceled.
|
|
Integration: Workflow Misc Part 2
Canceling since a higher priority waiting request for ci-refs/heads/main-integration-Workflow Misc Part 2 exists
|
|
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 Misc Part 2
The operation was canceled.
|
|
Integration: CLI Docker Build
Canceling since a higher priority waiting request for ci-refs/heads/main-integration-CLI Docker Build exists
|
|
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.
|
|
Integration: CLI Docker Build
The operation was canceled.
|
|
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 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: 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: 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 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/
|
|
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: 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 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 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 Add with dispatch-workflow Dependencies
No files were found with the provided path: test-result-integration-add-dispatch-workflow.json. No artifacts will be uploaded.
|
|
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: 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: 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: 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: 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/
|
|
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 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: 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/
|
|
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: 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 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/
|
|
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: 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/
|
|
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 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/
|
|
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 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 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/
|
|
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: 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)
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
|
848 Bytes |
sha256:6951eae543bad20b23212271c971326f1986f7ffc8deb7561984580ca75fc6a5
|
|
|
gh-aw-linux-amd64
Expired
|
10.6 MB |
sha256:89a4072b24cdb53c0a21c2d5c9ed23c28ee621be78700caa60c1a364db230f2c
|
|
|
test-result-integration-CLI Add & List Commands
Expired
|
5.11 KB |
sha256:db500b5cde301cb1a49f6df1954b0e38ba0d03b27d5c7c7ba301895baba86c99
|
|
|
test-result-integration-CLI Audit Logs & Firewall
Expired
|
1.42 KB |
sha256:3699fa8361b442636ba0433d6c3f9fc5f08c56687d8c22f24cb3b88ca8139ccc
|
|
|
test-result-integration-CLI Compile & Poutine
Expired
|
4.96 KB |
sha256:5b2c885e56645656f39fe8e86b9da7b4bfc305eee3fd6f4cafd11478d00d7359
|
|
|
test-result-integration-CLI Compile Workflows
Expired
|
8.54 KB |
sha256:8c4e6bd5d9cd2d4ac8e4a6b4ea8c5c70fdb163c1be242b4dfef8b136f1ae0705
|
|
|
test-result-integration-CLI Completion & Other
Expired
|
86.4 KB |
sha256:40084ce6d70323fde40ade72d6df564175d9f66e1344847f34bf5cd5cd6cadf6
|
|
|
test-result-integration-CLI Docker Build
Expired
|
451 Bytes |
sha256:f5e16415a9313e9fa440fa6435c8ee48b9c266573d51a20fa12d8b8ea9876c74
|
|
|
test-result-integration-CLI HTTP MCP Connect
Expired
|
737 Bytes |
sha256:7ef9e724f489e550e19838eaa91acc76404c1f931f4e2966e59eb10966b0c655
|
|
|
test-result-integration-CLI MCP Connectivity
Expired
|
1.23 KB |
sha256:7fdf354ba6d9ffc9fdc85163695c43bb1ff4df778fe0910f704498b744a94075
|
|
|
test-result-integration-CLI MCP Inspect GitHub
Expired
|
8.63 KB |
sha256:040c7bee109d284e453ce60a2101d630f269802fd8eeba11cc2095cc517b66ef
|
|
|
test-result-integration-CLI MCP Other
Expired
|
16.6 KB |
sha256:6b7d47383ff9aed26f2c782ac3deb8d8bd138c06e5e1a490c2cb74c7e3a1044b
|
|
|
test-result-integration-CLI Progress Flag
Expired
|
393 Bytes |
sha256:ee298370c396cc5a28dea37bc67fe6595e6f856895691f5066246386f6987b7c
|
|
|
test-result-integration-CLI Safe Update
Expired
|
4.55 KB |
sha256:61d77b7a8b13b0e142868fa47da4cc511657d2df5671415b61787607935e268a
|
|
|
test-result-integration-CLI Security Tools
Expired
|
1.55 KB |
sha256:b1c064d25f542a6d02ba1d7e851b92eb208a131a61abf8874fa2dec483a72ee5
|
|
|
test-result-integration-CLI Update Command
Expired
|
1.97 KB |
sha256:a4f65f62f7265ad42ff52e9de3d0a39be9e5840a385e067f24ffd1a942bdfa39
|
|
|
test-result-integration-CMD Tests
Expired
|
6.95 KB |
sha256:8f18f6fb413b9513689c7850c1df791e2fde64a947415d9689e30969c2a4dd6c
|
|
|
test-result-integration-Parser Location & Validation
Expired
|
2.79 KB |
sha256:a6a11ec1ba530481c1b3424de63e42948ef53cdc49d4a186a6dafe60ee416838
|
|
|
test-result-integration-Parser Remote Fetch & Cache
Expired
|
1.39 KB |
sha256:9bbd466fd73813c986a7f41b038ba57301119fae168b3e0566aab7ccdb523b28
|
|
|
test-result-integration-Workflow Actions & Containers
Expired
|
5.17 KB |
sha256:0975d5d0a3ae5d2f1171822b2176bce4c631b3bef2ac38011e6e29761dfa769d
|
|
|
test-result-integration-Workflow Compiler
Expired
|
8.29 KB |
sha256:158826d16d551607b8ba82ef03262ca0609daecc3f0a74478a9cef66895c3b42
|
|
|
test-result-integration-Workflow Features
Expired
|
41.1 KB |
sha256:2bb6674ff4024fe102d1943af82cc706ea5b3eba2a02feaf5b0c9d72789766f5
|
|
|
test-result-integration-Workflow Infra
Expired
|
24.6 KB |
sha256:70e7b4cfcbef6ad5c16b45840e6451883a46a0207a989b1229aff33e7de44862
|
|
|
test-result-integration-Workflow Misc Part 2
Expired
|
214 Bytes |
sha256:380ae089b0a73f119546439dac8056f180e707ac67b0e505cab41df5d6ac20c1
|
|
|
test-result-integration-Workflow Rendering & Bundling
Expired
|
24.7 KB |
sha256:6bb928c292ac01bfed50235a54515e380ca5ed89949c3c8a637b129f35e75fd7
|
|
|
test-result-integration-Workflow Tools & MCP
Expired
|
8.64 KB |
sha256:e7e2b632695c14c292565bd25b9940b00aa6b858fc08e49e0374ca42a862d9fb
|
|
|
test-result-integration-Workflow Validation
Expired
|
3.32 KB |
sha256:dc33219af9f208bc948c34a4225ff7a7ab373d71160fdf7608cc3b2a295da562
|
|
|
test-result-integration-unauthenticated
Expired
|
1.55 KB |
sha256:c7977df6a0d38d02f2c559fad83eb75fb6589204ed4ddf7b759a36d48f76ce77
|
|