The intl_pluralrules dependency was pinned to a patch level release in ba16827, but I can't find any justification for it rematining that way. Since then we'ne unpinned alll remaining 3rd party crates to minor version levels instead of patch levels to give more flexability to downstream builds. We only pin patch realeases for other things in this workspace that we can reasonably expect to match at any given point.
The commit bump to v7.0.1 also happened before the v7.0.2 release existed, and looking at the upstream commits doesn't suggest to me any reason we shouldn't let people start building against that.
The intl_pluralrules dependency was pinned to a patch level release in ba16827, but I can't find any justification for it rematining that way. Since then we'ne unpinned alll remaining 3rd party crates to minor version levels instead of patch levels to give more flexability to downstream builds. We only pin patch realeases for other things in this workspace that we can reasonably expect to match at any given point.
The commit bump to v7.0.1 also happened before the v7.0.2 release existed, and looking at the upstream commits doesn't suggest to me any reason we shouldn't let people start building against that.