Skip to content

Update argocd action to specify which repo it came from #11

Update argocd action to specify which repo it came from

Update argocd action to specify which repo it came from #11

Triggered via push August 5, 2024 15:28
Status Success
Total duration 5m 21s
Artifacts

build-push.yaml

on: push
Build and push images
4m 49s
Build and push images
Matrix: ArgoCD update automation
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Build and push images
The following actions uses Node.js version which is deprecated and will be forced to run on node20: docker/login-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
ArgoCD update automation (tembo-io/app-deploy, prod, prod-updates)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
ArgoCD update automation (tembo-io/app-deploy, staging, staging-updates)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
ArgoCD update automation (tembo-io/app-deploy-dev, dev, main)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/