-full variants of start and end times
-full variants of start and end times
tree-sitter to 0.26
tree-sitter-systemverilog to 0.3
tree-sitter-scala to 0.26
tree-sitter-rust-orchard to 0.16
tree-sitter-ocaml to 0.25
Does that hash-verify as well? And wouldn't we need to download and verify cargo-binstall anyways for that?
Sure. Since this is green, I'll remove it here. Perhaps we only run it when Cargo.toml is changed?
tree-sitter to 0.26
@wetneb Now there's a script that prints a table with suggestions of how to update the dependency. I also found cargo update --breaking which is unstable and works as I'd expect, so I added that...
tree-sitter-systemverilog to 0.3
tree-sitter-scala to 0.26
tree-sitter-rust-orchard to 0.16
tree-sitter-ocaml to 0.25
tree-sitter-lua to 0.5
tree-sitter-systemverilog to 0.3
tree-sitter-scala to 0.26
tree-sitter-rust-orchard to 0.16
tree-sitter-ocaml to 0.25
tree-sitter-lua to 0.5
cargo-outdated report to CI results
line_based_merge_parsed panicking when input sides contain conflicts (#763)
cargo-outdated report to CI results
cargo-outdated report to CI results
I'll work on a PR.
The way I do this for our projects is to have a cargo audit job in CI so that at least I bump when RUSTSEC advisories pop up (either for commited Cargo.lock files, latest, or `-Zminimal-version...
IMO, the main thing is not assuming target/debug is where the build happened.