BD103
BD103
> You'd probably do something like `cargo update --precise` to get the needed windows version. I tried using `cargo update --precise`, but I had some issues with duplicate dependencies. The...
For the period, you could definitely match what [Cargo does](https://lib.rs/crates/cargo) and publish for every stable release (as long as each release provides what nightly version they were pinned to at...
> > as long as each release provides what nightly version they were pinned to at that time > > How would you recommend to best provide this information? The...
> Offtopic: shouldn't [this](https://github.com/TheBevyFlock/bevy_cli/blob/1cb8e3a9c24c855994fba58ee199ccc9dce0df0d/.github/workflows/ci.yml#L76) be > > ``` > toolchain: ${{ needs.extract-rust-version.outputs.toolchain }} > ``` > > in your workflow file? For a second I thought so too, but [I...
> So I guess, I will add it to the `README` of the crates, so that it also shows up on the crates.io page when publishing. If that's too much...
> Won't the user have to specify the toolchain on the command line, e.g.: > > ``` > cargo +nightly-2024-10-03 install bevy_cli > ``` > > Or am I missing...
Thank you so much! :D
Here's my post: :)
Could you run `cargo update` and see if that fixes your issue? I think this happened to me before.
> Maybe we could download the blobs on CI test runs and let the tests pass locally if the blobs were not found? @BD103 I'm not sure I understand what...