feat(dependencies): add the Dependencies tab

[talissoncosta]

Thanks for submitting a PR! Please check the boxes below:

• I have read the Contributing Guide.
• I have added information to docs/ if required so people know about the feature.
• I have filled in the "Changes" section below.
• I have filled in the "How did you test this code" section below.

Changes

Closes #8427

A Dependencies tab in the Edit Feature modal: what gates this flag, and what it gates. Behind flag_dependencies.

Writes land immediately. There is no bulk endpoint, so a save button would loop POSTs and leave the tab half applied on the first refusal. The picker sits above the table rather than behind a button, matching Segment Overrides.

The picker drops the feature itself and anything already added, so the two refusals a user would hit most never fire. The other three surface their own message, which names both features and the rule they broke.

Per the issue, there is no "Must be" column and every dependency means "must be enabled". A row from a hand-written segment condition gets no remove control: the API will not delete it, and naming segments is out of scope for V1 per the issue's comments.

No change request handling. This issue is scoped to environments without them, so the tab also hides where they are enforced. Writing immediately would otherwise be a way to change a flag's gating without approval, through a route the rest of the modal closes. #8428 covers that case.

Fixtures. GET dependencies and dependents are not on main yet (#8570, #8571), so both serve fixtures behind a single useFixtures constant. Removing it, its two branches and the fixtures file leaves the real service behind. POST and DELETE have no fixture and fail until the API lands, which seemed more honest than faking a success.

Still blocked on one thing: DELETE .../dependencies/{prerequisite} does not exist. It is in the RFC at 2.3.2 and features.dependencies.deleted is already in the events catalogue, but there is no issue and no PR. The bin icon is in the mockups, so this cannot ship without it.

How did you test this code?

• Ran it. Checked all four states against the designs: clean slate, with prerequisites, as a prerequisite, and the unmet warning. Both themes.
• Running it caught a bug the linters could not: .alert lays its children out with flex, so each <strong> in the warning became a flex item and the text around it collapsed into "so<flag>is serving its disabled value in<environment>". Fixed in its own commit.
• No console errors from the tab. The forwardRef and moment warnings are pre-existing.
• tsc --noEmit and eslint --fix clean. The one constants.ts error is pre-existing on main, verified by stashing.
• Not tested against the real API, since three of the four endpoints are not on main.
• No E2E yet.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
docs	Error		Oct 1, 2026 1:37pm UTC
flagsmith-frontend-preview	Ready	Preview	Oct 1, 2026 1:37pm UTC
flagsmith-frontend-staging	Ready	Preview	Oct 1, 2026 1:37pm UTC

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}