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

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,20 +1,33 @@
1
- # Changelog
2
-
3
- ## 4.3.1
4
-
5
- - 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.
6
- - Corrected the documented Svelte minimum and clarified that consumer Admins and ProductOwners both need feedback-project assignments.
7
- - 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.
8
-
9
- ## 4.3.0
10
-
11
- - 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.
12
- - 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.
13
- - 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.
14
- - Board reads forward the optional access token and consume server-authorized item capabilities, including on empty lists. Status changes refresh filtered counts and pagination.
15
- - 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.
16
-
17
- ## 4.2.4
1
+ # Changelog
2
+
3
+ ## 4.3.3
4
+
5
+ ### Changed
6
+
7
+ - Feedback rows now keep the consuming app's standard border color for authorized Admins and ProductOwners. Editable status controls remain purple.
8
+ - The **Needs your input** cue remains visible when action is required; the redundant **You can change this status** cue has been removed.
9
+
10
+ ## 4.3.2
11
+
12
+ ### Added
13
+
14
+ - `<FeedbackDetail>` now renders the reporter's pasted **screenshot** (the new `BoardItem.screenshotUrl`) beneath the description, as a bounded thumbnail that opens the full image in a new tab. Previously the board never showed the submitter's screenshot — only reply-thread images. Requires the matching `status-feedback-admin` deploy that adds `screenshotUrl` to the public board item (a safe, own-origin URL; the server validates the scheme/origin). The package also applies a client-side scheme allowlist (`safeScreenshotSrc`: `https` or base64 raster `data:` image only) before putting the URL in the link — defense-in-depth so the shared widget never trusts the upstream blindly for a value it renders in an `<a href>`. Items without a screenshot are unaffected.
15
+
16
+ ## 4.3.1
17
+
18
+ - 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.
19
+ - Corrected the documented Svelte minimum and clarified that consumer Admins and ProductOwners both need feedback-project assignments.
20
+ - 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.
21
+
22
+ ## 4.3.0
23
+
24
+ - 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.
25
+ - 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.
26
+ - 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.
27
+ - Board reads forward the optional access token and consume server-authorized item capabilities, including on empty lists. Status changes refresh filtered counts and pagination.
28
+ - 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.
29
+
30
+ ## 4.2.4
18
31
 
19
32
  ### Fixed
20
33