Merged
Conversation
anelson
approved these changes
Jul 12, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Most notably,
darlingwas updated from0.20.10to0.21.0, which is one of the main dependencies of thebon-macroscrate. Since this was a breaking (in terms of cargo's semver) release, we need to release a new version (preferably a patch) ofbonto let downstream users benefit from an up-to-date version ofdarlingin their tree (or suffer, since they likely already have some dependencies that use0.20in their tree, so they'll start having several versions ofdarlingin their dependency tree, that can already be seen in the newCargo.lockin this PR 😢)