Add changelogs and tags

justfile

@@ -0,0 +1,10 @@
+default:
+  @just --list
+
+# Add a release tag and publish to the upstream remote. Need write privileges on the repository.
+tag crate version remote="upstream":
+  # A release tag is specific to a crate so following the convention crate-version.
+  echo "Adding release tag {{crate}}-{{version}} and pushing to {{remote}}..."
+  # Annotated tag.
+  git tag -a {{crate}}-{{version}} -m "Release {{version}} for {{crate}}"
+  git push {{remote}} {{crate}}-{{version}}

protocol/CHANGELOG.md

@@ -0,0 +1,5 @@
+# v0.4.0
+
+* Adds the `AsyncProtocol` high level interface for less boilerplate integration when using an async runtime (e.g. Tokio). Codes against the `futures-rs` traits, so any runtime which is compatible with those should be supported.
+* Aync read functions should now be cancellation safe.
+* The high level `Io` variant of the `ProtocolError` exposes if it is worth retrying with the V1 protocol with the new `ProtocolFailureSuggestion` type.

protocol/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "bip324"
-version = "0.3.1"
+version = "0.4.0"
 edition = "2021"
 license-file = "LICENSE"
 description = "Encrypted messaging over the Bitcoin P2P Protocol as specified by BIP 324"

proxy/CHANGELOG.md

@@ -0,0 +1,3 @@
+# v0.3.0
+
+* The new `--v1-fallback` flag allows a proxy connection to fallback to the V1 protocol if a remote doesn't support V2.

proxy/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "bip324-proxy"
-version = "0.2.0"
+version = "0.3.0"
 edition = "2021"
 license-file = "LICENSE"
 description = "BIP324 proxy enabling v1-only clients to use the v2 Bitcoin P2P Protocol"