Skip to content

error: use explicit matches for errors when the decision is crucial for correctness/performance #2719

error: use explicit matches for errors when the decision is crucial for correctness/performance

error: use explicit matches for errors when the decision is crucial for correctness/performance #2719

Triggered via pull request October 8, 2024 14:30
Status Success
Total duration 2m 40s
Artifacts

tls.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

1 warning
tls
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/