Skip to content

Infisical is the open-source platform for securing secrets, certificates, access, and AI Agents.

Merge remote-tracking branch 'origin/main' into capy/v3-remove-compat-react-select

andrewhuhh2a89198535b4
diff --cc frontend/src/components/V3_MIGRATION.md
index afca83dbb9,22cadd06fd..365f1c7949
--- a/frontend/src/components/V3_MIGRATION.md
+++ b/frontend/src/components/V3_MIGRATION.md
@@@ -117,8 -117,8 +117,8 @@@ All source anchors in this surface tabl
- `components/basic/InputField.tsx` is an unversioned legacy input, and `components/basic/Error.tsx` is a legacy error presentation used by `components/auth/Mfa.tsx`. Remove unused source or migrate the live caller; neither may be hidden by a rename.
- `components/integrations/NoEnvironmentsBanner.tsx`, `components/navigation/SecretDashboardPathBreadcrumb.tsx`, and `components/tags/CreateTagModal/CreateTagModal.tsx` are V2-dependent feature wrappers with no consuming module/symbol references at the baseline. Reverify and delete their unused implementation/export closure in a separate focused unit. The known outside-path completion gate includes these files.
- `pages/secret-manager/OverviewPage/components/SecretSearchInput/SecretSearchInput.tsx` and its barrel are an old Headless UI search control. Its sibling quick-search components are also consumed by the newer `ResourceSearchInput`; preserve those workflows while removing or replacing the old control.
- - `legacy.css`, imported by `index.css`, is the legacy palette. Migrate all remaining utility consumers before deleting it; deleting V2 React files alone is not a token cleanup proof.
+ - `legacy.css`, the legacy palette, is deleted. At `e434f2fdfdd608f97cd4041af84062991d2645cf` none of its color tokens had a literal utility, `--color-*` variable, `@apply` or `theme()` user in frontend sources, CSS, or config, so its default-palette overrides (`red`, `green`, `blue`, `yellow`) had no consumers either.
-- V3 `ReactSelect` is an independently implemented, token-based compatibility family, not a wrapper importing V2. Its deprecated status does not make every current consumer a V2 import. Do not use it as a cosmetic shortcut to avoid verifying Combobox behavior. Record custom option/group/creation/portal contracts and any replacement work before retiring `react-select`.
+- The V3 `ReactSelect` compatibility family (`FilterableSelect`, `CreatableSelect`) is deleted. Its consumers moved to `Combobox`, and none remained at `e434f2fdfdd608f97cd4041af84062991d2645cf`. The `react-select` package itself still has direct importers outside that directory; retire it only after those are gone.
- V3 `SecretInput`, `InfisicalSecretInput`, `SecretPathInput`, and `PasswordGenerator` have their own implementations. Compare security-sensitive behavior, not names. Removing unused V2 Editor/PasswordGenerator does not certify every active V3 editor flow.
- API/data versions such as `hooks/api/secretRotationsV2`, `BillingV2Page`, `PkiAlertsV2Page`, backend secret-v2 services and migration files are not automatically legacy UI. Their actual UI imports and implementations remain in scope; their legitimate API versions are not renamed.
- Third-party Radix, Lexical, Lottie, Font Awesome and react-select packages have current non-V2 consumers. A dependency is deleted only after its remaining ownership is proved; no package-name-based purge.
@@@ -310,5 -310,5 +310,4 @@@ After
- `audit-v2-ui.mjs --assert-zero` passes on that main commit. Review its detailed output and re-audit unversioned wrappers/feature primitives so the explicit outside-path list cannot conceal newly discovered legacy.
- The V2 source tree/barrel and every dead V2 helper are absent. No direct/deep/relative/dynamic/re-export path, alias, type dependency or V3 wrapper reaches a legacy implementation. Review file history/diffs for copied or cosmetically renamed code.
- Legacy styles and component-owned dependencies are removed after proving remaining consumer ownership. Legitimate API versions and independently supported V3 capabilities are disclosed rather than counted as UI exceptions.
--- Focused lint/types/build checks pass at the accepted head. Representative real rendered flows establish RBAC, hidden-value security, mutations, validation, keyboard/focus, nested overlay and portal lifetime, table/virtualization state and any active date/editor contracts. Synthetic screenshots and fixtures are distinguished from authenticated acceptance.
--- This ledger, lifecycle guidance, stories and design references reflect actual removed-on-main progress. An unresolved V2 family means the mission is **not complete**. Merge, preview deployment and production rollout are reported separately; no rollout claim follows from CI alone.
++- Focused lint/types/build checks pass at the accepted head. Representative real rendered flows establish RBAC, hidden-value security, mutations, validation, keyboard/focus, nested overlay and portal lifetime, table/virtualization state and any active date/editor contracts. Synthetic screenshots and fixtures are distinguished from authenticated acceptance.