Document destination handler reset fix in changelog

- TransactionParams::reset only cleared two of its fields, leaving
  stale acknowledged-mode state behind between transactions
- That state made the next transaction's Metadata PDU look like a
  duplicate, so it was silently dropped and the transfer never
  created its destination file

CHANGELOG.md

@@ -8,7 +8,14 @@ and this project adheres to [Semantic Versioning](http://semver.org/).
 
 # [unreleased]
 
-- Bumped `spacepackets` to v0.17
+- Bumped `spacepackets` to v0.18
+
+## Fixed
+
+- Destination handler's `TransactionParams::reset` now resets all fields instead of just two.
+  The incomplete reset left stale acknowledged-mode state behind, so a new transaction's Metadata
+  PDU was mistaken for a duplicate of an already-processed one and silently dropped, breaking
+  every transfer after the first one on a given destination handler instance.
 
 # [v0.3.0] 2025-09-25
 

src/dest.rs

@@ -257,8 +257,7 @@ impl<CheckTimer: Countdown> Default for TransactionParams<CheckTimer> {
 
 impl<CheckTimer: Countdown> TransactionParams<CheckTimer> {
     fn reset(&mut self) {
-        self.finished_params.reset();
-        self.anomaly_tracker.reset();
+        *self = Self::default();
     }
 }