Skip to content

ci: include bazel and bazelisk managers in renovate post-upgrade tasks #313

ci: include bazel and bazelisk managers in renovate post-upgrade tasks

ci: include bazel and bazelisk managers in renovate post-upgrade tasks #313

Triggered via pull request March 25, 2026 09:52
Status Success
Total duration 14s
Artifacts

dev-infra.yml

on: pull_request_target
issues
0s
issues
pull_request
7s
pull_request
post_approval_changes
10s
post_approval_changes
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
pull_request
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./github-actions/labeling/pull-request. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
post_approval_changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./github-actions/post-approval-changes. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/