Unleash / unleash / 25908143808

87%

master: 91%

push

github

chore: replace crypto.randomUUID() with uuid package (#12040)

## About the changes

This brings UUID generation in the frontend back behind the `uuid`
package instead of calling `crypto.randomUUID()` directly. The direct
browser API looked safe from a browser support perspective, but we
missed one important constraint: `crypto.randomUUID()` is only exposed
in secure contexts. That means it can be unavailable when the frontend
is served over plain HTTP, which can still happen in self-hosted or
local-network deployments.

The Node 20 migration replaced `uuid` with native `crypto.randomUUID()`
after confirming supported browsers implemented it, but that
compatibility check did not account for the HTTPS-only requirement. This
PR restores a browser-safe abstraction with `createUuid()`, using `uuid`
v4 generation underneath, and replaces the direct frontend call sites.

This is related to the deployment/runtime issue discussed in
https://github.com/orgs/Unleash/discussions/11863.

## Details

- Adds `uuid` as a direct frontend dependency.
- Adds `createUuid()` as the shared frontend UUID helper.
- Replaces direct `crypto.randomUUID()` usage in frontend UI state/id
generation paths.
- Keeps the config button accessibility description id stable across
re-renders.

## Verification

- `pnpm run lint:check`
- `pnpm run ts:check`
- `rg "crypto\.randomUUID\(\)" frontend/src` returns no direct frontend
usages.

1845 of 2040 branches covered (90.44%)

15075 of 17305 relevant lines covered (87.11%)

898.77 hits per line