Skip to content

Fix #6206: Update triage instructions for new label types #3521

Fix #6206: Update triage instructions for new label types

Fix #6206: Update triage instructions for new label types #3521

Triggered via pull request April 10, 2026 05:09
Status Success
Total duration 6m 53s
Artifacts 1

code_coverage.yml

on: pull_request
Check unit test completed
1m 34s
Check unit test completed
Compute changed files
55s
Compute changed files
Matrix: Run Code Coverage
Evaluate Code Coverage Reports
4m 6s
Evaluate Code Coverage Reports
Check Code Coverage Results
3s
Check Code Coverage Results
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
Check unit test completed
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ArcticLampyrid/action-wait-for-workflow@v1.3.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Compute changed files
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: abhinavsingh/setup-bazel@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Compute changed files
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Compute changed files
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Evaluate Code Coverage Reports
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: abhinavsingh/setup-bazel@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
final-coverage-report
359 Bytes
sha256:6c7fbd04aa7c37c914a9bbf94c794642ce39ee5ed639e40c0e84fdce6d534fa0