chore(deps): update actions/setup-node action to v6 #347
pr-checks.yml
on: pull_request
lint-protos
7s
buf-format
8s
buf-breaking-changes
7s
validate-schema
1m 6s
Annotations
1 error and 4 warnings
|
buf-breaking-changes
Failure: could not clone https://github.com/open-feature/schemas.git: stat .git/objects/pack/multi-pack-index.lock: file does not exist
stat .git/objects/pack/pack-c4b2068bd44a5e0678988e73318b2702699a48b9.idx: file does not exist
stat .git/objects/pack/pack-c4b2068bd44a5e0678988e73318b2702699a48b9.rev: file does not exist
stat .git/objects/pack/pack-f4cad43387cd10062727643b77b980b6d927fd0d.idx: file does not exist
stat .git/objects/pack/pack-c4b2068bd44a5e0678988e73318b2702699a48b9.pack: file does not exist
stat .git/objects/pack/pack-f4cad43387cd10062727643b77b980b6d927fd0d.pack: file does not exist
stat .git/objects/pack/pack-f4cad43387cd10062727643b77b980b6d927fd0d.rev: file does not exist
|
|
lint-protos
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bufbuild/buf-lint-action@v1, bufbuild/buf-setup-action@v1. 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/
|
|
buf-breaking-changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bufbuild/buf-breaking-action@v1, bufbuild/buf-setup-action@v1. 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/
|
|
buf-format
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bufbuild/buf-setup-action@v1. 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/
|
|
validate-schema
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@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/
|