Skip to content
build

Fix backward incompatible change of VPC endpoint names #431

Sign in to view logs

Fix backward incompatible change of VPC endpoint names

Fix backward incompatible change of VPC endpoint names #431

Re-run triggered October 19, 2023 08:25
@pierretrpierretr
#231
pierretr:master
Status Success
Total duration 43s
Artifacts –

ci.yaml

on: pull_request
security
56s
security
pre-commit
29s
pre-commit
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
security
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@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 (3.10)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@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 (3.9)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
pre-commit
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, pre-commit/action@v2.0.0. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/