Skip to content

docs(tutorial): Be more explicit about ParseError's role #531

docs(tutorial): Be more explicit about ParseError's role

docs(tutorial): Be more explicit about ParseError's role #531

Triggered via pull request July 29, 2024 17:17
Status Success
Total duration 42s
Artifacts

audit.yml

on: pull_request
security_audit
10s
security_audit
Matrix: cargo_deny
Fit to window
Zoom out
Zoom in

Annotations

1 error and 6 warnings
security_audit
Unable to publish audit check! Reason: HttpError: Resource not accessible by integration
security_audit
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/audit-check@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
security_audit
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions-rs/audit-check@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
security_audit
1 warnings found!
security_audit
It seems that this Action is executed from the forked repository.
security_audit
GitHub Actions are not allowed to use Check API, when executed for a forked repos. See https://github.com/actions-rs/clippy-check/issues/2 for details.
security_audit
Unknown warning kind unsound found, please, file a bug