Skip to content

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

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 #593

Triggered via pull request October 14, 2024 13:51
@muzarskimuzarski
synchronize #1083
Status Success
Total duration 5m 5s
Artifacts

semver_checks.yml

on: pull_request_target
semver-pull-request-check
4m 42s
semver-pull-request-check
semver-push-tag
0s
semver-push-tag
semver-pull-request-label
5s
semver-pull-request-label
Fit to window
Zoom out
Zoom in

Annotations

1 warning
semver-pull-request-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/