Skip to content

[CORE-47] Upgrade Swagger UI to 5.17.14 to resolve dompurify vulnerability. #320

[CORE-47] Upgrade Swagger UI to 5.17.14 to resolve dompurify vulnerability.

[CORE-47] Upgrade Swagger UI to 5.17.14 to resolve dompurify vulnerability. #320

Triggered via pull request October 17, 2024 23:54
Status Success
Total duration 8m 21s
Artifacts

verify_consumer_pacts.yml

on: pull_request
bump-check
3s
bump-check
regulated-tag-job  /  tag-job
9s
regulated-tag-job / tag-job
verify-consumer-pact
5m 36s
verify-consumer-pact
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
bump-check
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
regulated-tag-job / tag-job
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
verify-consumer-pact
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
verify-consumer-pact
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-java@v2, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
can-i-deploy
The following actions use a deprecated Node.js version and will be forced to run on node20: broadinstitute/[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/