You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should be able to release as soon as #386 and #373 are in.
the latter may require we release a new crate. @spacebear21 If you're willing to take this on, you should be able to edit this issue text directly. Let me know if you cannot.
Create a new minor release
Summary
This release enables transaction cut-through by allowing the receiver to add an arbitrary number of inputs and outputs, and allowing mixed input script types in Payjoin V2. Additionally, there are several changes to the payjoin directory API and the HPKE in an attempt to stabilize the V2 protocol. This release contains many breaking changes as a result.
We should be able to release as soon as #386 and #373 are in.
the latter may require we release a new crate. @spacebear21 If you're willing to take this on, you should be able to edit this issue text directly. Let me know if you cannot.
Create a new minor release
Summary
This release enables transaction cut-through by allowing the receiver to add an arbitrary number of inputs and outputs, and allowing mixed input script types in Payjoin V2. Additionally, there are several changes to the payjoin directory API and the HPKE in an attempt to stabilize the V2 protocol. This release contains many breaking changes as a result.
Commit
0aef52e
Changelog
contribute_witness_inputs
andcontribute_non_witness_inputs
in favor of a single consolidatedcontribute_inputs
functionInputPair
public to facilitate working with inputs in coin selection and input contributionsapply_fee
, which now requires a max_feerate parameter_danger-local-https
feature behind_
prefix so it doesn't show up in docs #423Checklist
Release numbering must follow Semantic Versioning. These steps assume the current
master
branch development version is MAJOR.MINOR.0.
On the day of the feature freeze
Change the
master
branch to the next MINOR+1 version:master
branch.bump-CRATE-MAJOR-MINOR+1
, eg.bump-CRATE-0-22
.bump-CRATE-MAJOR-MINOR+1
branch to the next development MINOR+1 version.Cargo.toml
version value toMAJOR.MINOR+1.0
.CHANGELOG.md
file.bump-CRATE-MAJOR-MINOR+1
branch tomaster
.bump-CRATE-MAJOR-MINOR+1
branch tomaster
.If any issues need to be fixed before the MAJOR.MINOR+1.0 version is released:
master
branch.bump-CRATE-MAJOR.MINOR+1
branch.bump-CRATE-MAJOR.MINOR+1
branch.On the day of the release
Tag and publish new release:
HEAD
commit in themaster
branch.CRATE-MAJOR.MINOR+1.0
--sign
flag.payjoin/rust-payjoin
repo.Release CRATE-MAJOR.MINOR+1.0
.1.0.0
release check the "Pre-release" box.The text was updated successfully, but these errors were encountered: