Maurice e9090fa33c fix(notices): confine the 4.0.0 release modal to the 4.0.x line ...

Without an upper bound it would greet somebody who jumped 3.x straight to
4.2 with a summary of a release they skipped, and it would run alongside
the next release's own notice.

maxVersion is exclusive, so 4.1.0 covers every 4.0.x patch. Pinned in the
registry test, together with the handover from the thank-you notice: at no
version may both be active.

2026-08-22 15:48:13 +02:00

..

conditions.test.ts

feat(config): put the operator-owned surfaces behind TREK_MANAGED (#1946)

2026-08-15 16:42:27 +02:00

registry.test.ts

fix(notices): confine the 4.0.0 release modal to the 4.0.x line

2026-08-22 15:48:13 +02:00

versionRange.test.ts

feat(system-notices): replace expiresAt with [minVersion, maxVersion) version gate

2026-04-17 20:03:23 +02:00