chore(deps): bump the all-dependencies group across 1 directory with 22 updates

[dependabot]

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[pomfrida]

@claude review

[claude]

Claude finished @pomfrida's task in 1m 37s —— View job

---

Review: dependency bump + formatting

Reviewed the full diff against origin/main. This is a low-risk Dependabot group bump. The large +1185/-1246 line count is misleading — almost none of it is behavioural.

What actually changed:

Part	Files	Notes
Version bumps	14 package.json + pnpm-lock.yaml	All patch/minor, no majors
Prettier 3.9 reformatting	29 .ts/.tsx (commit 7b44ea0)	Style only, semantically identical
ESLint --fix cleanup	Filter.test.tsx	Removed now-unused eslint-disable directives
Snapshot update	Autocomplete.test.tsx.snap (commit 927c15d)	Only styled-components hashed class names changed

✅ CI is green — all 5 workflows pass (Checks, Code Quality, React 18 compat, PR #5163, PR Title).

Dependency bumps — all safe

prettier 3.8.4→3.9.4, typescript-eslint 8.62→8.63, stylelint 17.13→17.14, react-hook-form 7.80→7.81, react-router-dom 7.18.0→7.18.1, downshift 9.3.6→9.4.0, styled-components 6.4.2→6.4.3, @figma/code-connect 1.4.8→1.4.9, browserslist, tsc-watch, @equinor/eds-mobile-components 0.2→0.3 (devDep only). No production major upgrades — nothing that should change runtime behaviour.

Source changes are formatting only

Two Prettier 3.9 style shifts account for the whole /next + component diff:

1. Union types collapse to one line and drop the leading | when they fit within print width — e.g. Icon.types.ts, Badge.types.ts, Chip.types.ts, Button.tsx, Typography/types.ts. The removed lines are pure reformatting; the types are unchanged.
2. Template-literal expressions break the ${ onto its own line when the interpolation wraps — e.g. Tab.tsx, Input.tsx. Again, no semantic change.

The .snap diff is expected: styled-components regenerates hashed class names on version bump, and only the hashes moved. Correctly regenerated in commit 927c15d.

One minor nit (non-blocking)

In packages/eds-data-grid-react/src/tests/Filter.test.tsx the removed eslint-disable-next-line directives left blank lines behind, and at :240 the explanatory comment is now orphaned:

// eslint complains about unneccessary cast, but HTMLElement != HTMLInputElement
                                    // ← disable directive removed; blank line left
const input = within(baseElement).getByTestId('input') as HTMLInputElement

The comment now points at a directive that no longer exists (typescript-eslint 8.63 evidently no longer flags this cast). Purely cosmetic — safe to tidy the stray blank lines and drop/update the stale comment, but not worth blocking the merge. Fix this →

Verdict

Safe to merge. Bumps are conservative, all changed source is auto-formatting, snapshot correctly regenerated, CI green. The one nit is cosmetic and optional.

---

• Read the diff
• Review dependency version bumps
• Review source file changes
• Post review
  • dependabot/npm_and_yarn/all-dependencies-74f1fdb1ce