Skip to content
gcr.io_mirror

[PORTER]gcr.io/ml-pipeline/cache-deployer:2.3.0 #4970

Sign in to view logs

[PORTER]gcr.io/ml-pipeline/cache-deployer:2.3.0

[PORTER]gcr.io/ml-pipeline/cache-deployer:2.3.0 #4970

Triggered via issue November 20, 2024 11:49
@YersiniaHerbYersiniaHerb
opened #4175 669c014
Status Success
Total duration 36s
Artifacts –

gcr.io_mirror.yml

on: issues
build
27s
build
auto_close_issues
2s
auto_close_issues
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
auto_close_issues
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
auto_close_issues
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
auto_close_issues
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/