Closed mfep closed 2 weeks ago
Thanks for letting us know; I am checking to see if I'm allowed to move the tag.
The release managers are on it (other libraries are also affected)
This appears to have been resolved, with the 1.85.0 tag now pointing at c11757 as expected
Summary
Git tags
boost-1.85.0
andboost-1.85.0.beta1
point to commite02cda69e4d070fd9b16a39282d6b5c717cb3da4
, which is the same as tagsboost-1.84.0
andboost-1.84.0.beta1
. I assume that this is a mistake, and the 1.85 tags should point to the latest commit onmaster
, of hashc11757decf393f6f1cf46f3f70b0bf892cdda5ee
.Apparently the
boost_1_85_0.tar.gz
downloadable from boost.org also includes the changes that are merged after the currentboost-1.85.0
tag.This discrepancy is problematic, since some packagers (e.g. vcpkg) pull Wave based on the tag name, therefore their users get an older version of Wave, even if the packaged Boost version is 1.85.
Expected
The
boost-1.85.0
git tag points to commitc11757decf393f6f1cf46f3f70b0bf892cdda5ee
.