Skip to content

Fix invalid cryptographic outputs in ws-security policies #186

Fix invalid cryptographic outputs in ws-security policies

Fix invalid cryptographic outputs in ws-security policies #186

Triggered via pull request October 16, 2024 10:56
Status Success
Total duration 2m 25s
Artifacts

pull-request.yml

on: pull_request
Run PR Build Workflow  /  Build on Ubuntu
1m 39s
Run PR Build Workflow / Build on Ubuntu
Run PR Build Workflow  /  Build on Windows
2m 10s
Run PR Build Workflow / Build on Windows
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
Run PR Build Workflow / Build on Ubuntu
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-java@v3, codecov/codecov-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Run PR Build Workflow / Build on Windows
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-java@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/