Skip to content

ci: Change cancel-in-progress to false in deploy workflow #131

ci: Change cancel-in-progress to false in deploy workflow

ci: Change cancel-in-progress to false in deploy workflow #131

Triggered via pull request May 12, 2026 15:08
@raymondkraymondk
opened #247
Status Success
Total duration 22s
Artifacts –

internal_vs_external.yml Required

on: pull_request_target
check-repo-policies  /  ...  /  Check Is Bot
16s
check-repo-policies / check-is-bot / Check Is Bot
Check Revoke Approvals
0s
Check Revoke Approvals
Check Unallowed File Changes
0s
Check Unallowed File Changes
Check CLA
0s
Check CLA
check-repo-policies  /  Check Bot Policies
check-repo-policies / Check Bot Policies
Fit to window
Zoom out
Zoom in

Annotations

1 warning
check-repo-policies / check-is-bot / Check Is Bot
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/setup-python@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/