pinkforest(she/her)

rustsec-admin brings this comrak also brought it out via default-features initially

FWIW - I've used if:'s under job's to solve similar before: https://docs.github.com/en/actions/using-jobs/using-conditions-to-control-job-execution You can do check-if job and then in assign-ids jobs you can match if: based on what happened...

FWIW - It's not fixed The :ghost: is still with us :chains: after https://github.com/rustsec/advisory-db/pull/1332 https://github.com/rustsec/advisory-db/pull/1336 Also PRs typically run in the github action that is in the PR so it...

The ghost :ghost: has not been annoying us :chains: for a while so yes it seemed to have disappeared indeed. Good stuff :partying_face:

@kellytk if you don't mind mind we could use a test crate that includes all sorts of code that should not be included but current cargo-geiger includes so we can...

I just dug Win10 ISO from M$ for free.. down the rabbithole I go :) Rust does offer toolchain for gnu thus cargo should be fine with it and related...

I asked @Shnatsel about it yesterday and was supportive as well to under rustsec org

It's a bug #93 Cargo de-coupling and CLI options mirror will fix this for 0.12.0

@Shnatsel - would love your feedback on this :unicorn:

I edited to propose Deprecated status which would be more of a gentle nudge to switch off from the crate in near future.