Skip to content

chore(deps): update neo4j docker tag to v5 #532

chore(deps): update neo4j docker tag to v5

chore(deps): update neo4j docker tag to v5 #532

Triggered via pull request October 19, 2024 10:02
Status Success
Total duration 1m 29s
Artifacts

devops.yml

on: pull_request
Prettier
6s
Prettier
Renovate Config Validator
1m 22s
Renovate Config Validator
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Prettier
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/
Prettier
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/
Renovate Config Validator
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/
Renovate Config Validator
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/