Add CHANGELOG.md, and append 0.4.0 release notes - #48
Conversation
| - Allow to set `aad` in `StorableBuilder::{build, deconstruct}` (#40). | ||
| - Pass the `data_encryption_key` by reference to `StorableBuilder::{build, deconstruct}` (#40). | ||
| - Replace LDK's `chacha20poly1305` implementation with the rust-bitcoin implementation (#42). | ||
| - Rename `vss-client` crate to `vss-client-ng` (#46). |
There was a problem hiding this comment.
Let's move this into a dedicated section to highlight the new name and location.
| - Bump MSRV to 1.75.0 (#38). | ||
| - Allow to set `aad` in `StorableBuilder::{build, deconstruct}` (#40). | ||
| - Pass the `data_encryption_key` by reference to `StorableBuilder::{build, deconstruct}` (#40). | ||
| - Replace LDK's `chacha20poly1305` implementation with the rust-bitcoin implementation (#42). |
There was a problem hiding this comment.
I don't think we need to include this. Can we generally structure the CHANGELOG along the lines of 'API changes' / 'Bug fixes'? This and similar PRs probably don't even need to be mentioned as they are purely internal refactors and shouldn't make any difference to the user.
| - Pass the `data_encryption_key` by reference to `StorableBuilder::{build, deconstruct}` (#40). | ||
| - Replace LDK's `chacha20poly1305` implementation with the rust-bitcoin implementation (#42). | ||
| - Rename `vss-client` crate to `vss-client-ng` (#46). | ||
| - Enable `reqwest` client-level timeouts (#39). |
There was a problem hiding this comment.
Could mention that we set default HTTP timeouts now.
| @@ -0,0 +1,13 @@ | |||
| # 0.4.0 - Nov 11, 2025 | |||
| - Enforce that all implementations of `VssHeaderProvider` are `Send+Sync` (#35). | |||
There was a problem hiding this comment.
Ah, I think I was off-by-one when I created the v0.3.1 tag. That did ship with 0.3.1 already.
tnull
left a comment
tnull
left a comment
There was a problem hiding this comment.
I guess you should also bump the version number in Cargo.toml in this PR?
58cd70d to
241207c
Compare
241207c to
9ef78a3
Compare
9ef78a3 to
4d1c80d
Compare
2 participants
No description provided.