Bump library version + add changelog

[thunderbiscuit]

This PR bumps the libraries to their release versions and adds the changelog entry for 3.1

[reez]

Two nits, otherwise good!

[reez]

Should this get changed to [Unreleased](https://github.com/bitcoindevkit/bdk-ffi/compare/v3.1.0...HEAD) ?

[thunderbiscuit]

Yep thanks!

[reez]

We can remove this, nothing is wrong with the automated changelog, but the background for this is I asked to squeeze it into the 3.0.0 last minute #1010 (comment) and then it sort of overlapped a bit with the general addition of the automated changelog label stuff

[thunderbiscuit]

Ah yes I see. Cool!

[thunderbiscuit]

I'll wait and merge #1113 first, then rebase this branch onto master and merge then.

[reez]

I'll wait and merge #1113 first, then rebase this branch onto master and merge then.

Cool, just ACK'd 1113

[thunderbiscuit]

@reez would you mind taking another look at this one? That'll set me up for cutting and pushing the tag.

[j-kon]

Could we include the Psbt::finalize fix from #1015 and the foreign-UTXO validation change from #1030 in this section? Both are part of the 3.1 release diff and affect observable behavior; #1015 is also labeled changelog: fixed and explicitly provided a release-note entry.

[thunderbiscuit]

Will reply on the main thread!

[reez]

@reez would you mind taking another look at this one? That'll set me up for cutting and pushing the tag.

ACK with this comment: For #1015 and #1030 it looks like they were generated by the changelog automation I think but you removed them so I’m assuming you did that for a specific reason so up to you if you want to add them back in or not?

[thunderbiscuit]

Sorry guys I removed those from the auto-generated notes because they were not quite changelog worthy at first glance (the auto-generation only grabs the PR title and puts it in the category defined by the label).

• Bumping miniscript to a patch is not a line in the changelog directly, it should come in in the header-type section where we define the libraries' versions directly. Miniscript is not in this group at the moment, but I think it would actually be worth adding. A worthy changelog line IMO has to be something specific that was fixed, not the bump itself. This is the case here indeed, and I just didn't realize so apologies for that. I'll add it for sure!
• Same for 1030. Reading it I thought it was just the bump in bdk_wallet to 3.1.0, but actually the PR contained a small fix as well. I'll update the changelog.

Note that we could also decide that important library version updates should come into the ## Added section as well as individual entries. We just haven't done that in the past.

[reez]

Sorry guys I removed those from the auto-generated notes because they were not quite changelog worthy at first glance (the auto-generation only grabs the PR title and puts it in the category defined by the label).

• Bumping miniscript to a patch is not a line in the changelog directly, it should come in in the header-type section where we define the libraries' versions directly. Miniscript is not in this group at the moment, but I think it would actually be worth adding. A worthy changelog line IMO has to be something specific that was fixed, not the bump itself. This is the case here indeed, and I just didn't realize so apologies for that. I'll add it for sure!

• Same for 1030. Reading it I thought it was just the bump in bdk_wallet to 3.1.0, but actually the PR contained a small fix as well. I'll update the changelog.

Note that we could also decide that important library version updates should come into the ## Added section as well as individual entries. We just haven't done that in the past.

Sounds good, got my ACK so feel free to merge whenever you're ready

[thunderbiscuit]

@j-kon @reez thanks for the review guys!