Skip to content
staging-pipeline

Feature cluster matching #1946

Sign in to view logs

Feature cluster matching

Feature cluster matching #1946

Triggered via pull request October 16, 2024 16:03
@CarlosQ96CarlosQ96
synchronize #1862
feature_cluster_matching
Status Success
Total duration 19m 49s
Artifacts –

staging-pipeline.yml

on: pull_request
Run linters
49s
Run linters
test
18m 37s
test
publish
0s
publish
deploy
0s
deploy
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Run linters
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Run linters
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v1, wearerequired/lint-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/
test
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test
The following actions use a deprecated Node.js version and will be forced to run on node20: aws-actions/configure-aws-credentials@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/