Skip to content

Conversation

@tcharding
Copy link
Member

@tcharding tcharding commented Oct 30, 2025

Do some clean ups then bump the version number, add a changelog entry, and update the lock files.

@tcharding tcharding changed the title Release tracking PR: bitreq 0.2.0 Release tracking PR: bitreq v0.2.0 Oct 30, 2025
@jamillambert
Copy link
Collaborator

Reviewed b08cf2c, all good.

@tcharding tcharding force-pushed the push-rpmkoqtvvnzq branch 2 times, most recently from 52cd6e1 to 696c2a9 Compare November 5, 2025 03:43
Remove the `minreq` changelog and add a changelog entry for the
already released 0.1.0

Note I forgot to grab a commit hash when forking, that is a fail on my
part.
I wrote this example stub when trying to add WASM support to the
`minireq` fork (my first fork of `minreq` that was used as a basis of
`bitreq`). It should never have been included in the crate import into
this repo.
Put a dash between the version number and the date in all the
changelog files where it is missing - woops.
In preparation for release bump the version number, add a changelog
entry, and update the lock files.

Also depend on the new version in all local crates.
@tcharding tcharding marked this pull request as ready for review November 5, 2025 03:47
Copy link
Collaborator

@jamillambert jamillambert left a comment

Choose a reason for hiding this comment

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

ACK 6e4de32

@tcharding tcharding merged commit 4c03a69 into rust-bitcoin:master Nov 5, 2025
30 checks passed
@tcharding
Copy link
Member Author

Tagged and published.

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.

2 participants