Skip to content

Update dependency i18next-cli to ^1.75.1 (main) - #6947

Open
red-hat-konflux[bot] wants to merge 1 commit into
mainfrom
konflux/mintmaker/main-main/i18next-cli-1.x
Open

red-hat-konflux[bot] wants to merge 1 commit into
mainfrom
konflux/mintmaker/main-main/i18next-cli-1.x

Conversation

@red-hat-konflux

@red-hat-konflux red-hat-konflux Bot commented Oct 11, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
i18next-cli ^1.74.4 → ^1.75.1 age confidence

Release Notes

i18next/i18next-cli (i18next-cli)

v1.75.1

Compare Source

  • fix(extract): types and values read through a namespace import resolve like named imports. With
    import * as Types from './types', a qualified type ((color: Types.Color) => …, x as Types.Color,
    FC<Types.Props>, declare const s: Types.Status) and a namespace member (Types.SIZES.map(…),
    Types.Status.Done, t(Types.LABELS.save), Object.keys(Types.LABELS)) now extract their keys, also
    for a namespace re-exported from a barrel (export * as Shared from './types'). Fixes
    #​305.
  • fix(extract): an exported as const object resolves in the files that import it: t(LABELS.save) and
    Object.keys(LABELS) only worked in the declaring file before.
  • fix(extract): a value typed keyof typeof MAP resolves to the map's keys, so
    t(`label.${key}`) with declare const key: keyof typeof LABELS extracts label.save and
    label.cancel. This branch never matched before.

v1.75.0

Compare Source

  • feat(extract): new extract.maxTypeDepth option sets how many levels of nested object members are
    followed when a dynamic key reads a typed value (default: 5). Higher values cost time and memory on
    large recursive types such as OpenAPI schemas. Requested in
    #​302.
  • fix(extract): the depth now counts from the type an indexed access picks instead of from the declared
    wrapper type. type Pet = components['schemas']['Pet'] gets the full depth below Pet, where the
    components/schemas wrapper used to take two of the five levels.
  • fix(extract): numeric keys resolve in object types and indexed access types, so openapi-typescript
    response types work:
    operations['getPet']['responses'][200]['content']['application/json'] and
    op.responses[200].content['application/json'].status resolved nothing before.

v1.74.8

Compare Source

  • fix(extract): a commented template literal no longer extracts its placeholder as a key.
    // t(`QUARTER.${q}`) extracted QUARTER.${q} and // t(`status.${deepObject.status}`) extracted
    status.${deepObject.status}. Such a comment now keeps the existing keys it matches (QUARTER.1,
    QUARTER.2, …) even with removeUnusedKeys, the way a commented static key keeps its key, while code can
    still add new matching keys. A pattern without any static part (`${a}.${b}`) is ignored. Fixes
    #​304.

v1.74.7

Compare Source

  • fix(extract): a selector i18nKey on <Trans t={t}> now routes into the hook's namespaces the same way
    t() does, matching react-i18next 17.0.16. With const { t } = useTranslation(['ns1', 'ns2']),
    <Trans t={t} i18nKey={$ => $.ns2.message} /> was filed as ns1:ns2.message; it is now filed as
    ns2:message, like t($ => $.ns2.message). Under types.enableSelector: 'strict' a leading primary
    namespace is stripped too (useTranslation('only') with $ => $.only.key files only:key). Reported in
    react-i18next#1933.
  • fix(extract): the props of a component typed React.FC<Props> (also FC, FunctionComponent),
    forwardRef<Ref, Props>(…) or memo<Props>(…) are typed by Props, and iterating a typed member binds
    the element. props.colors.map((color) => t(\Color.${color}`))withcolors: Color[]extracted nothing before unlesscolorwas asserted withas Color. Arrays of objects work the same way: props.items.map(({ kind }) => …), for (const item of props.items)and a destructured({ items }) => items.map(…)`. Fixes #​303.

v1.74.6

Compare Source

  • fix(extract): iterating an inline array literal binds the element like iterating a named constant
    does. ([1, 2, 3, 4] as const).map((q) => t(\QUARTER.${q}`)), for (const unit of ['day', 'hour'] as const)`
    and inline arrays of objects extracted nothing before. Fixes
    #​301.
  • fix(extract): members of nested object types resolve. t(\barStatus.${deepObject.Bar.status}`)andt(`fooBarStatus.${deepObject.Foo.Bar.status}`) now extract the nested union's values, also through references to other types, optional chaining (pet.category?.kind), destructuring (const { kind } = pet.category) and indexed access types (DeepObject['Bar']['status'], components['schemas']['Pet']), so types generated by openapi-typescript work. Nested members are followed up to five levels below the declared type, as in components.schemas.Pet.category.kind`.
    Fixes #​302.

v1.74.5

Compare Source

  • fix(extract): a value typed as an array of a string union (Color[], readonly Color[],
    Array<Color> or an alias of one) now resolves to the union's values, so
    colors.map((color) => t(\color.${color}`))andfor (const color of colors)extract every key instead of nothing. Before, this only worked withcolor as Color`. Fixes
    #​300.

Configuration

📅 Schedule: (in timezone America/New_York)

  • Branch creation
    • "every weekend"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

To execute skipped test pipelines write comment /ok-to-test.


Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

@coderabbitai

coderabbitai Bot commented Oct 11, 2026 •

Copy link
Copy Markdown

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration
  • Configuration used: Repository: stolostron/console/.coderabbit.yaml
  • Review profile: CHILL
  • Plan: Enterprise
  • Run ID: 71881eb4-efe1-411f-a025-cef32ea2a72b

📥 Commits

Reviewing files that changed from the base of the PR and between 0ba23c9 and f739a1b.


⛔ Files ignored due to path filters (1)
  • frontend/package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)
  • frontend/package.json

Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 8 remain after this review.



📝 Walkthrough

Walkthrough

The frontend i18next-cli development dependency range changes from ^1.74.4 to ^1.75.1.

Changes

Frontend dependency update

Layer / File(s) Summary
Update i18next-cli version range
frontend/package.json
The declared i18next-cli development dependency range changes from ^1.74.4 to ^1.75.1.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~2 minutes


Merge Risk: ⚪ Minimal · up to f739a

The dependency update is ready to merge with no identified installation or runtime risk.

Pre-merge checks | Passed 4 | Failed 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check Warning The description explains the dependency update and includes release notes, but it does not follow the repository template. It omits the ticket summary, ticket link, change type, AI contribution, and r… Update the description to include all required template sections. Add the ticket summary, ticket link, type of change, AI contribution, completed general checklist, and relevant verification or test results.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check Passed The title clearly identifies the primary change: upgrading the i18next-cli dependency to ^1.75.1. The trailing branch reference is minor noise but does not prevent understanding.
Docstring Coverage Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.

Full details: Description check

Explanation

The description explains the dependency update and includes release notes, but it does not follow the repository template. It omits the ticket summary, ticket link, change type, AI contribution, and required checklist responses.


  • Fix all pre-merge checks with AI
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR


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

@openshift-ci

openshift-ci Bot commented Oct 11, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: red-hat-konflux[bot]
Once this PR has been reviewed and has the lgtm label, please assign randy424 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@red-hat-konflux
red-hat-konflux Bot force-pushed the konflux/mintmaker/main-main/i18next-cli-1.x branch 3 times, most recently from 0ba23c9 to c6a946b Compare October 12, 2026 00:19
@red-hat-konflux red-hat-konflux Bot changed the title Update dependency i18next-cli to ^1.75.0 (main) Update dependency i18next-cli to ^1.75.1 (main) Oct 12, 2026
@red-hat-konflux
red-hat-konflux Bot force-pushed the konflux/mintmaker/main-main/i18next-cli-1.x branch 7 times, most recently from 34ac92b to 473dabd Compare October 12, 2026 00:24
Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
@red-hat-konflux
red-hat-konflux Bot force-pushed the konflux/mintmaker/main-main/i18next-cli-1.x branch from 473dabd to f739a1b Compare October 12, 2026 00:24
@openshift-ci

openshift-ci Bot commented Oct 12, 2026

Copy link
Copy Markdown

@red-hat-konflux[bot]: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/check f739a1b link true /test check

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants