@alliance-droid/status-feedback-system 4.2.4 → 4.3.1

package/CHANGELOG.md

@@ -1,12 +1,26 @@
 # Changelog
 
-## 4.2.4
+## 4.3.1
+
+- Documentation: added a [4.3 consumer upgrade guide](README.md#upgrading-to-43) to the README shipped in the npm package. It identifies affected custom proxies, shows how to delegate tokens on board reads, and explains how to diagnose missing status controls.
+- Corrected the documented Svelte minimum and clarified that consumer Admins and ProductOwners both need feedback-project assignments.
+- Runtime behavior is unchanged from 4.3.0. Affected consumers must apply the proxy changes in their own app; installing this documentation patch does not modify host routes.
 
-### Fixed
+## 4.3.0
 
-- `<FeedbackDetail>` now reloads responses when consumers keep the detail panel mounted and select a different feedback item. The previous item's responses are cleared while the new thread loads, and stale in-flight requests can no longer overwrite the currently selected item's responses.
+- Security: refreshed dependencies and raised the Svelte peer minimum to 5.55.7. The matching admin update requires feedback-scoped access tokens and explicit project assignments for consumer Admins as well as ProductOwners.
+- Consumer boards now restrict Admins and assigned ProductOwners to accepting, reopening, and declining work. Only acceptance can initiate automation; engineering and release transitions stay in the admin app.
+- Editable items have purple status controls and row accents, with a text cue. The privileged **Needs my input** filter shows Open, Considering, and Waiting on reply across all pages.
+- Board reads forward the optional access token and consume server-authorized item capabilities, including on empty lists. Status changes refresh filtered counts and pagination.
+- Requires the matching `status-feedback-admin` board capabilities update. Deploy the admin server first; custom consumer proxies must forward the optional board `Authorization` header and `status=needs_input` filter.
 
-## 4.2.3
+## 4.2.4
+
+### Fixed
+
+- `<FeedbackDetail>` now reloads responses when consumers keep the detail panel mounted and select a different feedback item. The previous item's responses are cleared while the new thread loads, and stale in-flight requests can no longer overwrite the currently selected item's responses.
+
+## 4.2.3
 
 ### Changed