@redacto.io/consent-sdk-react 10.0.0-beta.11 → 10.0.0-beta.12

package/CHANGELOG.md

@@ -1,383 +0,0 @@
-# @redacto.io/consent-sdk-react
-
-## 10.0.0-beta.11
-
-### Minor Changes
-
-- 43ea923: route the standard notice-content fetch through the Go ledger (ledgerBaseUrl); the magic-link flow (applicationId) and sandbox sessions stay on the consent server. Per-language audio uses the ledger when configured, except sandbox sessions, which the ledger's X-Consent-Token auth does not support
-
-  drop the separate ledger check-consent round-trip: the notice read already returns the per-principal reconsent overlay (`purpose_selections` / `reconsent_required`) inline, so the banner consumes it directly. This also fixes reconsent on a republished notice, which the standalone check-consent overlay could not detect (no notice-version awareness), and makes `validate_against` apply to the overlay
-
-### Patch Changes
-
-- f4b3cad: Inline notice read: use the authenticated `notices/{notice_uuid}` endpoint whenever an access token is available, so the embedded widget works against the Go consent ledger.
-
-  The inline widget read the notice from `notices/get-notice/{notice_uuid}` — a tokenless endpoint the consent server serves and the ledger does not. Pointing `baseUrl` at the ledger therefore failed with 404 `Resource not found` even though the notice existed there, and the path is compiled into the SDK so no `baseUrl` change could fix it.
-
-  The inline widget already carries the access token it needs to submit consent. When that token is present the notice now comes from `notices/{notice_uuid}` with an `Authorization: Bearer` header — the same endpoint the modal (`RedactoNoticeConsent`) has always used, served by both the consent server and the ledger, and the one that returns the caller's `purpose_selections` / `reconsent_required` overlay and 409 `CONSENT_ALREADY_PROVIDED`. Without a token the legacy tokenless path is unchanged, so the OTP-gated assisted flow and any anonymous embed keep working against the consent server.
-
-  Because the token now selects the endpoint, a token that arrives after the widget mounts also has to re-read the notice: `InlineController.updateToken()` refetches when the first read was tokenless, so the unauthenticated content can no longer be auto-submitted. A later token refresh does not refetch, which would discard in-progress selections.
-
-  A token arriving while the first read is still in flight leaves two reads racing, so the notice read is now generation-guarded in `InlineController` — a superseded tokenless response can no longer replace the authenticated content, reset the selections under the user, or auto-submit against the newly stored token. `hasAlreadyConsented` is also cleared at the start of each read, so a 409 for one principal cannot blank the widget for the next one.
-
-  Also in this change: `Accept-Language` is sent on the tokenless read too (it was only set on the authenticated path in `consent-sdk-js` and `consent-sdk-react`, so `language` was ignored for anonymous callers), and the `consent-sdk-react` notice fetch is now abort-guarded like `consent-sdk-react-native`, so the tokenless request cannot resolve last and overwrite the authenticated one.
-
-- udpate the beta version with latest changes
-
-## 10.0.0-beta.10
-
-### Patch Changes
-
-- refactor(privacy-center): remove purpose revocability, keep the revoke warning message (CON-I1041). Removes only the non-revocable withdrawal-blocking behaviour from feature #490: the Privacy Center no longer consumes a per-purpose `revocable` flag, no longer disables the withdraw control for non-revocable purposes, and no longer maps the `purpose_not_revocable` backend error to a toast. `PurposeItem` drops `revocable`. The per-purpose custom `revoke_warning_message` shown in the revoke modal is **retained** (`PurposeItem` keeps `revoke_warning_message`). Paired with the consent-server and redfront changes; revocability moves to the notice level.
-
-## 10.0.0-beta.9
-
-### Patch Changes
-
-- e44b1a3: Privacy Center: fix the DSAR request form showing "No products available" against the legacy Python backend. The request-form product picker is now sourced from `user-consents` on **both** backends — the Go ledger's `/public/.../user-consents` when `ledgerBaseUrl` is configured, Python's `/dsar/privacy-center/user-consents` otherwise (the same read the Manage Consent view already used in both modes) — instead of being skipped entirely without a ledger, which left the picker dependent on `form/data` product groups that Python no longer emits.
-
-  Two related gaps are closed: a successful-but-empty `user-consents` response no longer overwrites the product groups `form/data` did supply, and a backend that returns only the legacy flat `purposes` list now renders those purposes under a single "Your data" group instead of the empty state. Cases raised from that fallback group are submitted without a `product_uuid` anchor, matching the pre-grouping org-level case shape.
-
-- source Privacy Center DSAR product picker from user-consents on both backends
-
-## 10.0.0-beta.8
-
-### Patch Changes
-
-- fix(consent-sdk): record language on withdraw/regrant + localize RN activity log
-
-## 10.0.0-beta.7
-
-### Minor Changes
-
-- feat(consent-sdk-react): show User ID as primary field in shared-contact profile picker
-
-## 10.0.0-beta.6
-
-### Patch Changes
-
-- minor bug fix in beta version
-
-## 10.0.0-beta.5
-
-### Major Changes
-
-- M3 Version
-
-### Minor Changes
-
-- 1a11423: RedactoNoticeAssisted: add `ledgerBaseUrl` support with the standard fallback, for parity with RedactoNoticeConsent and RedactoNoticeConsentInline. When `ledgerBaseUrl` is set, the consent write is routed through `ledgerBaseUrl || baseUrl || BASE_URL` (only `submit-consent` moves to the ledger; the public notice / OTP / TTS endpoints stay on `baseUrl`). After OTP verification the widget also runs a ledger `check-consent` read and, if the principal has already fully consented, hands off via `onComplete` without writing a duplicate consent event — the ledger equivalent of the legacy Python 409 `CONSENT_ALREADY_PROVIDED`, which no longer fires once consent records live in the ledger. Without `ledgerBaseUrl` the behavior is unchanged (write to the legacy consent server, reactive 409-as-success). The ledger `check-consent` network read is now shared across all three notice components.
-
-### Patch Changes
-
-- 1a11423: RedactoNoticeConsentInline: detect already-consented principals via the Go ledger after the consent cutover. Previously the embedded widget only recognized an already-consented user through Python's 409 `CONSENT_ALREADY_PROVIDED` on `get-notice`; once consent records move to the ledger, Python stops returning that 409, so the widget would re-render the notice and could auto-submit a duplicate consent. When `ledgerBaseUrl` is configured (and outside the magic-link `specific_uuid` flow), the widget now runs the same ledger `check-consent` read the banner uses and short-circuits to the already-consented state, gating auto-submit until that read settles. Without `ledgerBaseUrl` the legacy Python-409 path is unchanged. The ledger `check-consent` read is now shared between `RedactoNoticeConsent` and `RedactoNoticeConsentInline`.
-
-## 10.0.0-beta.4
-
-### Patch Changes
-
-- 05b3452: fix(privacy-center): make the org logo visible and even in the header
-
-  PCAvatar applied its coloured fill to the `<img>` branch as well as the initials branch. Since every
-  call site passes `color="info"` and branding maps `--pc-info` to the org's own primary colour, a
-  brand-coloured logo on a transparent background was painted onto a disc of the same colour and
-  disappeared. Image avatars now render with `object-fit: contain` (no more stretching) and
-  `box-sizing: border-box` (unchanged 24/32/48px box), and fall back to initials when the logo fails to
-  load instead of showing an empty coloured circle. Standalone brand marks get a neutral surface and a
-  hairline ring; a new `framed={false}` opts out of that chrome when a parent control already draws it.
-
-  The header's logo menu is now a real navbar control: it uses the same size token, ring, background
-  and hover as the notification bell (`--pc-navbar-actions-control-height`, 32px circle), instead of an
-  ad-hoc transparent pill wrapping a smaller 24px avatar. That removes the size mismatch next to the
-  bell and the concentric rings its brand-tinted hover glow used to stack around the avatar's own ring.
-
-- 31785c6: Remove Bhojpuri (`bho`) from the language selectors and bundled translations. The backend no longer
-  supports Bhojpuri (it is not a DPDPA-mandated language), so it is dropped from the Privacy Center and
-  Notice language lists to match the supported set. Any consumer still passing `bho` falls back to the
-  default language.
-- Privacy Center: 400 error when DP changes language to Bhojpuri
-
-## 10.0.0-beta.3
-
-### Minor Changes
-
-- show org_user_id to distinguish shared-contact profiles
-
-## 10.0.0-beta.2
-
-### Minor Changes
-
-- add revokable and non revokable purposes
-
-## 10.0.0-beta.1
-
-### Major Changes
-
-- feat(privacy-center): shared-contact profile picker (OTP + embeddable SDK)
-
-### Minor Changes
-
-- 61d18e8: fix(privacy-center): resolve mobile/org_user_id as contact for mobile-only logins
-
-### Patch Changes
-
-- 8145b3d: Privacy Center: when `ledgerBaseUrl` is not provided, consent reads/writes (user-consents, group purposes, manage-consent, receipts list, receipt PDF) fall back to the legacy Python `/dsar/privacy-center` endpoints and payloads instead of 404ing against `${baseUrl}/public/...`, and the DSAR form's ledger picker overlay is skipped. Fixes the Privacy Center showing "No Data" for integrations without a deployed Go ledger.
-
-## 10.0.0-beta.0
-
-### Major Changes
-
-- route consent writes & Privacy Center reads through the Go ledger (ledgerBaseUrl)
-
-## 9.4.0
-
-### Minor Changes
-
-- 9f7f7d5: feat(consent-sdk-react): add RedactoNoticeAssisted (agent-assisted OTP consent) + starter loan demo
-- add notice assisted and fix ui/ux
-
-## 9.4.0-beta.0
-
-### Minor Changes
-
-- feat(consent-sdk-react): add RedactoNoticeAssisted (agent-assisted OTP consent) + starter loan demo
-
-## 9.3.0
-
-### Minor Changes
-
-- 0642145: show empty blank screen when no data visible
-
-### Patch Changes
-
-- bd3c598: fix(consent-sdk-react): restore erasure consent-revoke confirmation modal
-- fix(consent-sdk-react): restore erasure consent-revoke confirmation modal
-
-## 9.3.0-beta.1
-
-### Patch Changes
-
-- fix(consent-sdk-react): restore erasure consent-revoke confirmation modal
-
-## 9.3.0-beta.0
-
-### Minor Changes
-
-- show empty blank screen when no data visible
-
-## 9.2.0
-
-### Minor Changes
-
-- 06a735c: keep revoked-consent purposes raisable in privacy-center DSAR forms
-- Refactor Privacy Center UX: remove "active" qualifier from product chip purpose counts, implement single-select product chips with an inline purpose panel, redesign the grouped DSAR product picker experience, and add a fully internationalized "My Receipts" tab for consent receipt management.
-- 45b7b2b: download receipt and product level grievance form
-
-### Patch Changes
-
-- b132a29: fix(consent-sdk-react): drop "active" qualifier from product chip purpose count
-
-## 9.2.0-beta.3
-
-### Minor Changes
-
-- Refactor Privacy Center UX: remove "active" qualifier from product chip purpose counts, implement single-select product chips with an inline purpose panel, redesign the grouped DSAR product picker experience, and add a fully internationalized "My Receipts" tab for consent receipt management.
-
-## 9.2.0-beta.2
-
-### Patch Changes
-
-- fix(consent-sdk-react): drop "active" qualifier from product chip purpose count
-
-## 9.2.0-beta.1
-
-### Minor Changes
-
-- download receipt and product level grievance form
-
-## 9.2.0-beta.0
-
-### Minor Changes
-
-- keep revoked-consent purposes raisable in privacy-center DSAR forms
-
-## 9.1.0
-
-### Minor Changes
-
-- remove hard coded 30 days values
-
-## 9.0.0
-
-### Major Changes
-
-- bugs fix
-
-## 8.0.0
-
-### Major Changes
-
-- enhance ui/ux
-
-## 7.3.0
-
-### Minor Changes
-
-- change branding path
-
-## 7.2.0
-
-### Minor Changes
-
-- bugs fix
-
-### Patch Changes
-
-- 7df3e20: Thread the clicked card's `product_uuid` through the privacy center's revoke/regrant/renew flow so purposes shared across multiple product cards mutate the correct card instead of falling back to action-implied scoping (which is ambiguous when two cards share the same state). Adds an optional `productUuid` parameter to the public `manageConsent` API; existing callers that omit it keep the prior server-side fallback behaviour.
-
-## 7.1.0
-
-### Minor Changes
-
-- update responsivenss
-
-## 7.0.0
-
-### Major Changes
-
-- configurable privacy center SDK
-- 331cbad: Apply org-level branding in `RedactoPrivacyCenter`. The privacy center now fetches `/user/api/0/public/org-branding/by-slug/{slug}` on mount and uses the response to:
-  - Swap the sidebar header avatar for the org's `icon_url` (collapsed) or wide `logo_url` (expanded).
-  - Show `brand_name` as the sidebar title.
-  - Hide the "Powered by Redacto" footer when `hide_platform_branding` is `true`.
-  - Apply the org's `theme` colors at runtime as `--pc-*` CSS custom-property overrides on `document.documentElement`. Primary/secondary hover and active variants are auto-derived. Cleared on unmount so the host page reverts to defaults.
-
-  **Breaking changes:**
-  - Removed dark mode from the privacy center. `ThemeProvider`, `useTheme`, `ThemeToggle`, and `ThemeTransitionOverlay` are deleted, the `[data-theme="dark"]` CSS block is gone, and the moon/sun toggle no longer appears in the navbar.
-  - Removed the `theme` prop from `RedactoPrivacyCenter`. The privacy center is now light-only; org-branding theme colors are applied on top.
-
-  Falls back to the previous initials avatar, slug-derived name, and SDK default colors when the branding response is unavailable.
-
-## 6.0.0
-
-### Major Changes
-
-- update Manage Consent
-
-## 5.3.0
-
-### Minor Changes
-
-- notification hub
-
-## 5.2.0
-
-### Minor Changes
-
-- docs update
-
-## 5.1.0
-
-### Minor Changes
-
-- update docs
-
-## 5.0.0
-
-### Major Changes
-
-- add privacy center sdk
-
-## 4.0.0
-
-### Major Changes
-
-- add privacy center sdk to react native and react
-
-## 3.6.0
-
-### Minor Changes
-
-- refactor payload to add language
-
-## 3.5.0
-
-### Minor Changes
-
-- add legacy api
-
-## 3.4.0
-
-### Minor Changes
-
-- feat: added notce 2.0
-
-## 3.3.0
-
-### Minor Changes
-
-- update support for submit API
-
-## 3.2.0
-
-### Minor Changes
-
-- enhance PurposeItem component to track initial data elements
-
-## 3.1.0
-
-### Minor Changes
-
-- purpose expiry for null validity
-
-## 3.0.0
-
-### Major Changes
-
-- downgrade react version in sdk
-
-## 2.1.0
-
-### Minor Changes
-
-- accessibility voice over cahnges
-
-## 2.0.0
-
-### Major Changes
-
-- added accessibility
-
-## 1.4.0
-
-### Minor Changes
-
-- fix language scroll issue
-
-## 1.3.0
-
-### Minor Changes
-
-- fix language scroll issue
-
-## 1.2.0
-
-### Minor Changes
-
-- chore: updated API routes
-
-## 1.1.0
-
-### Minor Changes
-
-- feat: add accessibility and fixes transalations
-
-## 1.0.0
-
-### Major Changes
-
-- Inline consent sdk added
-
-### Patch Changes
-
-- 0eac64c: Added base url as prop