Skip to content
Continuous Integration

Problem: version is not aligned with release #112

Sign in to view logs

Problem: version is not aligned with release

Problem: version is not aligned with release #112

Triggered via pull request October 16, 2024 02:01
@mmsqemmsqe
opened #101
mmsqe:bump_version
Status Failure
Total duration 30s
Artifacts –

ci.yml

on: pull_request
cargo check
20s
cargo check
cargo test
19s
cargo test
cargo fmt
10s
cargo fmt
cargo clippy
20s
cargo clippy
cargo audit
11s
cargo audit
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 5 warnings
cargo audit
Unable to publish audit check! Reason: HttpError: Resource not accessible by integration
cargo audit
Critical vulnerabilities were found, marking check as failed
cargo audit
The following actions use a deprecated Node.js version and will be forced to run on node20: rustsec/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
cargo audit
2 vulnerabilities found!
cargo audit
7 warnings found!
cargo audit
It seems that this Action is executed from the forked repository.
cargo 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.