Skip to content
CI/CD Pipeline

fix: heroku branch from main to master #2

Sign in to view logs

fix: heroku branch from main to master

fix: heroku branch from main to master #2

Triggered via push September 21, 2024 15:12
@hotungkhanhhotungkhanh
pushed 669ba6d
deploy
Status Failure
Total duration 47s
Artifacts –

ci-cd.yml

on: push
build
22s
build
deploy
11s
deploy
Fit to window
Zoom out
Zoom in

Annotations

1 error and 4 warnings
deploy
Process completed with exit code 128.
build
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-node@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
deploy
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
deploy
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/