Remove doc_auto_cfg and release 0.2.2#197
Merged
apoelstra merged 3 commits intorust-bitcoin:0.2.xfrom Nov 26, 2025
Merged
Conversation
Leave doc_cfg there, even though we are suspicious of it, since it is already there.
82e1324 to
e15702b
Compare
Note that the Rust MSRV is 1.56.1 but our script checks the *cargo* version which is 1.56.0.
e15702b to
8109ece
Compare
Member
Author
|
I cannot run my local CI on this because it doesn't have committed lockfiles, but IMO we should just ship it. Aside from being "obviously correct", it's tested in other projects which do have committed lockfiles, so we'll quickly know if anything goes wrong. |
tcharding
approved these changes
Nov 25, 2025
Member
Author
|
Tagged and published. |
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.
Should unblock various projects depending on hex-conservative 0.2.x.