Skip to content
OSSAR

Fix incorrect switching to https when receiving BEP34 TCP preference #620

Sign in to view logs

Fix incorrect switching to https when receiving BEP34 TCP preference

Fix incorrect switching to https when receiving BEP34 TCP preference #620

Triggered via pull request November 24, 2024 13:23
@CorralPeltzerCorralPeltzer
synchronize #304
preserve-tcp-scheme
Status Success
Total duration 2m 25s
Artifacts –

ossar-analysis.yml

on: pull_request
OSSAR-Scan
2m 14s
OSSAR-Scan
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
OSSAR-Scan
The following actions uses node12 which is deprecated and will be forced to run on node16: github/ossar-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
OSSAR-Scan
The following actions use a deprecated Node.js version and will be forced to run on node20: github/ossar-action@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
OSSAR-Scan
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/