kaafil-react-uikit 0.10.3 → 0.11.1

package/CHANGELOG.md

@@ -6,6 +6,54 @@ The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this package uses [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 While on `0.x` a minor bump may carry a breaking change; the entry will say so.
 
+## [0.11.1] — 2026-09-15
+
+### Changed
+
+- Peer floor moves to `kaafil-js@^0.6.2`. 0.6.0 and 0.6.1 both mishandled a
+  `204 No Content` — 0.6.0 threw on the missing envelope, 0.6.1 threw inside
+  `attachMeta` and the failure was classified as a transport error and
+  RETRIED, so a successful withdraw ran twice and surfaced the second
+  attempt's `404`. Withdraw is unusable below 0.6.2.
+
+## [0.11.0] — 2026-09-15
+
+The peer range moves to `kaafil-js@^0.6.0`, which is where `files.remove()`
+lands — on 0.5.x the new control would be a `TypeError`, not a `404`. The
+engine must also be running a build with `deleteFile`; against an older one the
+call answers `404`.
+
+### Added
+
+- **A filed trip document can be withdrawn.** There was no delete at any layer
+  — engine, SDK or kit — so a permit uploaded by mistake stayed visible to
+  every traveller on the trip until retention removed it, and `purgeAt` is
+  `null` unless the agency configured a TTL. In the default case that meant
+  forever.
+
+  `useFiles()` gains `remove(fileId, version)`. `TripDocumentsSection` offers
+  a **Withdraw** control, and offers it ONLY where the engine will allow it:
+  `trip_document` that is not already purged. The other three purposes are
+  evidence owned by a parent record that decides its own life — a receipt by
+  its expense, an attachment by its form field, a voucher by its booking — so
+  those rows show nothing rather than a button that would answer `422`.
+
+  It confirms first, and the dialog names the two consequences a reader cannot
+  infer from the word "withdraw": the file leaves storage rather than being
+  hidden, and anyone already holding a link loses access immediately, because
+  the object a signed URL points at is gone. The action is irreversible and
+  that is the only honest place to say so.
+
+  The control is danger-coloured on hover only. A document list with a
+  permanently red control on every line is a list nobody reads; the colour
+  arrives when the pointer does.
+
+### Fixed
+
+- `.kf-trip-documents-section__link-button` now carries `:hover:not(:disabled)`
+  and an explicit `:disabled`, the same guard 0.10.3 put on the dialog's
+  primary button and for the same reason.
+
 ## [0.10.3] — 2026-09-15
 
 ### Fixed