Upgrade libflate 2.3.0 (was 2.1.0) - #35
Merged
Merged
Conversation
SOF3
approved these changes
Apr 15, 2026
Contributor
Author
|
I took the liberty to push the required |
Owner
|
Under what circumstances would this become a problem though? If you already have a lockfile, the yanked version should remain possible to download, and if you don't hvae a lockfile, libflate should just auto update. |
Contributor
Author
|
Thank you very much for the very fast turn around and release 👏
You are correct, cargo seems to resolve properly the new I guess my PR is more about making things explicit then 👍 |
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.
context: dealing with the aftermath of the core2 dependency being yanked
https://github.com/sile/libflate/releases/tag/v2.3.0