(Please see linked issue in egui_miniquad for more context)
I want to release one of my projects on crates.io, which requires that all of my deps are fully published to crates.io as well. Currently, I need to use a version of puffin and puffin_http that is newer than the last release 0.19.0, which I am doing so by adding a [patch.crates-io] section to my Cargo.toml. This is a problem, since cargo publish ignores that and then I get broken builds. (Note: removing the [patch] section just gives me different errors since git deps aren't allowed).
Solution
I'd like to ask that a new release be uploaded, so that the fixes (which have already been merged into puffin/main) get published to crates.io, where I and others can use them in our own packages.
Alternatives
As far as I can tell there aren't any: crates.io has a requirement that all other deps must be published, with no way around it.
emilk
commented
3 months ago
Problem
(Please see linked issue in
egui_miniquadfor more context)I want to release one of my projects on
crates.io, which requires that all of my deps are fully published tocrates.ioas well. Currently, I need to use a version ofpuffinandpuffin_httpthat is newer than the last release0.19.0, which I am doing so by adding a[patch.crates-io]section to myCargo.toml. This is a problem, sincecargo publishignores that and then I get broken builds. (Note: removing the[patch]section just gives me different errors sincegitdeps aren't allowed).Solution
I'd like to ask that a new release be uploaded, so that the fixes (which have already been merged into
puffin/main) get published tocrates.io, where I and others can use them in our own packages.Alternatives
As far as I can tell there aren't any:
crates.iohas a requirement that all other deps must be published, with no way around it.Additional context
212, #213 : Changes I'm referring to that I need
egui_miniquadfor the same reason of publishing my crate