Skip to content

fix: Cron logs metadata #601

fix: Cron logs metadata

fix: Cron logs metadata #601

Triggered via pull request November 25, 2024 11:25
Status Success
Total duration 19m 48s
Artifacts

ci_code_review.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Code Review
Your workflow is using a version of actions/cache that is scheduled for deprecation, actions/cache@v1. Please update your workflow to use the latest version of actions/cache to avoid interruptions. Learn more: https://github.blog/changelog/2024-09-16-notice-of-upcoming-deprecations-and-changes-in-github-actions-services/
Smoke Test / Test dev
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@1f9a0c22da41e6ebfa534300ef656657ea2c6707, azure/login@92a5484dfaf04ca78a94597f4f19fea633851fa2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Code Review
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Code Review
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-java@v3, stCarolas/setup-maven@v4.5, actions/cache@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/