Bump i18next-cli from 1.66.2 to 1.67.2 in /frontend in the i18n group

[dependabot]

Bumps the i18n group in /frontend with 1 update: i18next-cli.

Updates i18next-cli from 1.66.2 to 1.67.2

Changelog

Sourced from i18next-cli's changelog.

1.67.2

• fix(lint): broaden the checkConcatenation JSX detection to flag any ≥2 adjacent translation units rendered as direct siblings — a <Trans> component or a {t(...)} expression. This now catches <Trans>…</Trans>{t('…')}, {t('a')}{t('b')} and two <Trans> separated only by whitespace, in addition to the previous "<Trans> … text … <Trans>" case. Single translations next to plain literal text or punctuation are still not flagged (#275).

1.67.1

• feat(lint): lint.checkConcatenation now accepts a severity level in addition to a boolean: 'error' reports concatenation issues as errors so the lint command exits non-zero (fails CI), 'warn' (or true, the default) reports them as non-failing warnings, and 'off' (or false) disables the check. Previously the concatenation check could only warn; making it fail the build required a custom plugin (#275).

1.67.0

• feat(lint): detect string concatenation involving translated strings, an i18n anti-pattern that breaks in languages which reorder or inflect the pieces. The linter now flags JavaScript concatenation where an operand is a t() call (e.g. t('greeting') + ', ' + name) and sentences split across multiple <Trans> components joined by literal text (e.g. <p><Trans>…</Trans> and <Trans>…</Trans></p>). It deliberately does not flag t() used only as a nested call argument (e.g. arr.indexOf(t('x')) + 1) or concatenation inside t() arguments (e.g. t('prefix.' + suffix)). Enabled by default; disable with lint.checkConcatenation: false (#275).
• feat(lint): lint issues now carry an optional severity ('error' | 'warning'). Concatenation issues are reported as warnings — they are printed but do not fail the run (the lint command exits non-zero only when there are errors), so adding this check does not break existing CI pipelines. Hardcoded-string and interpolation issues remain errors. Plugins may set severity on the issues they emit (defaults to 'error' when omitted).

Commits

• aea509c 1.67.2
• d86cb6f fix(lint): flag >=2 adjacent translation units in JSX concatenation (#275)
• 15a7577 1.67.1
• ca015bb feat(lint): allow lint.checkConcatenation to set severity (error/warn/off) (#...
• c5a699d 1.67.0
• 7a63d39 feat(lint): warn on string concatenation in translations (#275)
• See full diff in compare view

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