fix: update eligibility check to include user creation date for revie… #1052
iib0011push-docker.yml
on: push
build-and-push-backend
2m 57s
build-and-push-frontend
3m 4s
Annotations
5 errors and 2 warnings
|
build-and-push-backend
Canceling since a higher priority waiting request for docker-build-Build and Push Docker Images-refs/heads/main exists
|
|
build-and-push-backend
The operation was canceled.
|
|
build-and-push-frontend
Canceling since a higher priority waiting request for docker-build-Build and Push Docker Images-refs/heads/main exists
|
|
build-and-push-frontend
The operation was canceled.
|
|
Build and Push Docker Images
Canceling since a higher priority waiting request for docker-build-Build and Push Docker Images-refs/heads/main exists
|
|
build-and-push-backend
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
build-and-push-frontend
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|