Version bump quinn to enforce patched quinn-proto

[finnbear]

Now crates like wtransport, that only depend on quinn and use quinn-proto via quinn::proto, can point to a patched version.

[Ralith]

cargo update (or the default behavior when adding a new dependency) will be sufficient to get the latest quinn-proto regardless, so I'm not sure this is strictly needed. Still, no harm, and I wouldn't mind getting #1977 published.

[finnbear]

cargo update

FWIW, once your nightly library code base has hundreds of dependencies, cargo update (or removing Cargo.lock) becomes hazardous (e.g. introduces incompatibilities due to SEMVER mistakes and changing nightly features) and it's safer to depend on exact versions of dependencies and manually update the important ones occasionally (but you can only do that with direct dependencies, not transitives ones).

[Ralith]

cargo update can also target individual transitive dependencies if you don't want to do everything at once.

[finnbear]

cargo update can also target individual transitive dependencies if you don't want to do everything at once.

You're right, but if you use your library in 5 different places (say you use your game engine in 5 different games), then you would have to remember to run cargo update --package quinn-proto in those 5 places (where the Cargo.lock files live).

Maybe this is really niche 😂

[djc]

• Published quinn-proto v0.11.8 at registry crates-io
• Published quinn v0.11.5 at registry crates-io
• [new tag] quinn-0.11.5 -> quinn-0.11.5
• [new tag] quinn-proto-0.11.8 -> quinn-proto-0.11.8
• Release notes