Version numbering reset for wreq and wreq-util #1254

We have completed the version-number reset for both wreq and wreq-util.

We are sorry that this requires a manual change for downstream users. When the project was renamed from rquest to wreq, we continued with wreq 5.x and later published 6.0 release candidates. In hindsight, those version numbers did not clearly reflect that the public API is still evolving. We should have corrected this before users had to depend on the old ranges.

Current stable releases

The current stable versions are:

• wreq 0.16.0, with release notes
• wreq-util 0.2.0, with release notes

For a new or updated manifest, use:

[dependencies]
wreq = "0.16"
wreq-util = "0.2"

Keep any feature flags you already use. Because the old and new versions are different Cargo compatibility ranges, Cargo cannot apply this reset automatically. After editing Cargo.toml, run cargo update.

Stable release mapping

The previous stable releases were republished under the new scheme without starting a new API line:

If you need the previous stable API line, wreq-util 0.1.0 supports wreq >=0.15.1, <0.16. The current line is wreq 0.16.x with wreq-util 0.2.x.

Yanked and frozen releases

The old stable wreq 5.x and wreq-util 2.2.x releases have been yanked. Existing lockfiles can continue to use a yanked version, but Cargo will not select it when creating a new lockfile. Please update your manifest even if an existing build still works.

The wreq 6.0.0-rc.* and wreq-util 3.0.0-rc.* release lines are frozen and will not receive further updates. Development continues from the stable wreq 0.16.0 and wreq-util 0.2.0 releases instead.

Versioning from here

While the public API is still changing, wreq will remain below 1.0. Breaking API changes will move to a new minor line, such as 0.16 to 0.17. Compatible fixes will use patch releases within the same line. wreq-util will keep its own pre-1.0 series and state which wreq line it supports.

We know this forced migration creates extra work for maintainers and users. We apologize for the disruption. If the change causes a dependency resolution or compatibility problem, please report it here with the relevant part of your Cargo.toml and Cargo's error message.