Build and Review PR #23 #36
build-and-review-pr.yml
on: pull_request
build-and-review-pr
/
setup
7s
create-cache
14s
build-and-review-pr
/
build-and-review-pr
19s
test
11s
Annotations
6 errors and 8 warnings
|
build-and-review-pr / build-and-review-pr
Unhandled error: HttpError: Resource not accessible by integration
|
|
build-and-review-pr / build-and-review-pr
Before this PR can be merged, the following item(s) should be addressed to comply with the action's Contributing Guidelines.
- Please update the action's version in the Usage Examples section of README.md. Each instance of this action should be updated to:
`uses: im-open/restore-cache@v1.3.2`
- Please ensure the action has been recompiled by running the following command from the root of the repository:
`npm run build`
|
|
test
Process completed with exit code 1.
|
|
test
Process completed with exit code 1.
|
|
test
Cache not found for input keys: nuget-b4a8e54a5693f5c5785b42a05e312049edd721a7158750bacf472165c0e71920
|
|
test
Cache not found for input keys: abc123
|
|
build-and-review-pr / setup
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: im-open/.github/.github/actions/did-custom-action-code-change@v1, im-open/git-version-lite@v2. 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/
|
|
create-cache
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-dotnet@v3. 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/
|
|
build-and-review-pr / build-and-review-pr
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: im-open/.github/.github/actions/update-action-version-in-file@v1. 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/
|
|
test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./, actions/checkout@v4. 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/
|
|
test
Failed to restore: Cache service responded with 400
|
|
test
Failed to restore: Cache service responded with 400
|
|
test
Failed to restore: Cache service responded with 400
|
|
test
Failed to restore: Cache service responded with 400
|