Skip to content

Update bitcoinconsensus dependency#1165

Merged
sanket1729 merged 1 commit intorust-bitcoin:masterfrom
tcharding:08-04-update-bitcoinconsensus
Aug 4, 2022
Merged

Update bitcoinconsensus dependency#1165
sanket1729 merged 1 commit intorust-bitcoin:masterfrom
tcharding:08-04-update-bitcoinconsensus

Conversation

@tcharding
Copy link
Copy Markdown
Member

We recently released a couple of new versions of
rust-bitcoinconsensus, the first was mainly to move to git subtree,
included in this release was a bump of the patch version of bitcoin
core. The next release updated bitcoin core major version to 0.20.2

Update our bitcoinconsensus dependency to 0.20.2-0.5.0.

We recently released a couple of new versions of
`rust-bitcoinconsensus`, the first was mainly to move to git subtree,
included in this release was a bump of the patch version of bitcoin
core. The next release updated bitcoin core major version to 0.20.2

Update our bitcoinconsensus dependency to `0.20.2-0.5.0`.
@tcharding tcharding mentioned this pull request Aug 3, 2022
3 tasks
@tcharding tcharding added this to the 0.29.0 milestone Aug 3, 2022
Copy link
Copy Markdown
Member

@apoelstra apoelstra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK 7f55477

@tcharding tcharding added the P-high High priority label Aug 4, 2022
Copy link
Copy Markdown
Member

@sanket1729 sanket1729 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK 7f55477

@sanket1729 sanket1729 merged commit 9bac1a0 into rust-bitcoin:master Aug 4, 2022
@tcharding tcharding deleted the 08-04-update-bitcoinconsensus branch August 5, 2022 02:32
apoelstra added a commit that referenced this pull request Aug 8, 2022
110b5d8 Bump version to v0.29.0 (Tobin C. Harding)

Pull request description:

  Add changelog notes and bump the version number to v0.29.0.

  ## Notes

  I attempted to go through all the PRs since last release, please sing out if you had a PR merged that is not mentioned and you would like it mentioned.

  The changelog notes can be changed or improved, please do not take me writing them to imply I know exactly what goes on round here - I just made an effort to save others having to do it.

  ## TODO
  - [x]  merge all 'required' PRs
    - #1131
    - #1137
    - #1129
    - #1151
    - #1165 (add release notes still)
  - [x] Ensure all green from the CI run on: rust-bitcoin/rust-miniscript#450
  - [ ] Carry out (and improve) the #1106

ACKs for top commit:
  tcharding:
    ACK 110b5d8
  Kixunil:
    ACK 110b5d8
  apoelstra:
    ACK 110b5d8
  sanket1729:
    reACK 110b5d8

Tree-SHA512: d00c70534476794c01cd694ea9a23affef947c4f913b14344405272bc99cc00763f1ac755cc677e7afbd3dbef573d786251c9093d5dbafd76ee0cf86ca3b0ebd
@Kixunil
Copy link
Copy Markdown
Collaborator

Kixunil commented Oct 25, 2022

Oh, this one broke no_std for users with bitcoinconsensus. And we released it. 🤦‍♂️ Since nobody complained maybe nobody has such use case but we should fix it anyway.

@apoelstra
Copy link
Copy Markdown
Member

Oof. Could we get CI to check on this?

TBH I don't know anyone personally who is using bitcoinconsensus, with std or not.

@tcharding
Copy link
Copy Markdown
Member Author

Oh, this one broke no_std for users with bitcoinconsensus. And we released it.

Its the "incompatible feature combinations" thing you are referring to, right?

#840

@Kixunil
Copy link
Copy Markdown
Collaborator

Kixunil commented Oct 26, 2022

@tcharding no, I guess the bitcoinconsensus feature is missing in no_std test.

@tcharding
Copy link
Copy Markdown
Member Author

Oh, ok. I'll take a look.

@tcharding
Copy link
Copy Markdown
Member Author

cargo +nightly build --target thumbv7m-none-eabi fails on every tag in rust-bitcoinconsensus back to v0.17.1

Please see: #1352

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants