refactor: apply same refresh to Bridge Integration #748
chrisdoehringmain.yml
on: push
vars
4s
deploy_dev
/
deploy
Matrix: deploy_dev_legacy
Waiting for pending jobs
deploy_prod
/
deploy
30d 0h
Matrix: deploy_prod_legacy
Annotations
7 errors and 3 warnings
|
deploy_prod_legacy (celery-beat) / deploy
The deployment was rejected or didn't satisfy other protection rules.
|
|
deploy_prod_legacy (celery-deployments-worker) / deploy
The deployment was rejected or didn't satisfy other protection rules.
|
|
deploy_prod_legacy (celery-worker) / deploy
The deployment was rejected or didn't satisfy other protection rules.
|
|
deploy_prod_legacy (celery-permissions-worker) / deploy
The deployment was rejected or didn't satisfy other protection rules.
|
|
deploy_prod_legacy (cdip-portal) / deploy
The deployment was rejected or didn't satisfy other protection rules.
|
|
deploy_prod / deploy
The deployment was rejected or didn't satisfy other protection rules.
|
|
Build and deploy admin-portal
The strategy configuration was canceled because "deploy_prod_legacy.celery-beat" failed
|
|
vars
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/
|
|
build / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v5, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3, google-github-actions/auth@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/
|
|
deploy_stage / deploy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, azure/setup-helm@v3, google-github-actions/auth@v2, google-github-actions/get-gke-credentials@v2, google-github-actions/setup-gcloud@v2, slackapi/slack-github-action@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/
|