Skip to content

chore(deps): pin dependencies - #139

Merged
openshift-merge-bot[bot] merged 1 commit into
masterfrom
konflux/mintmaker/master/nodejs
Aug 21, 2026
Merged

chore(deps): pin dependencies#139
openshift-merge-bot[bot] merged 1 commit into
masterfrom
konflux/mintmaker/master/nodejs

Conversation

@red-hat-konflux-kflux-prd-rh02

@red-hat-konflux-kflux-prd-rh02 red-hat-konflux-kflux-prd-rh02 Bot commented Aug 18, 2026

Copy link
Copy Markdown

This PR contains the following updates:

Package Type Update Change Pending Age Confidence
@commitlint/cli (source) devDependencies pin ^21.2.121.2.2 age confidence
@commitlint/config-conventional (source) devDependencies pin ^21.2.021.2.2 age confidence
@testing-library/user-event devDependencies patch 14.6.414.6.5 age confidence
i18next-cli devDependencies minor 1.69.01.70.1 1.71.0 (+3) age confidence

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

⚠️ Renovate's pin functionality does not currently wire in the release age for a package, so the Minimum Release Age checks can apply. You will need to manually validate the Minimum Release Age for these package(s).

Add the preset :preserveSemverRanges to your config if you don't want to pin your dependencies.


Release Notes

testing-library/user-event (@​testing-library/user-event)

v14.6.5

Compare Source

Bug Fixes
i18next/i18next-cli (i18next-cli)

v1.70.1

Compare Source

  • feat: further namespace detection improvements
    (#​284):
    • ReturnType<typeof useTranslation<'ns', 'keyPrefix'>>['t'] on parameters (plain and
      destructured) is treated like TFunction<'ns', 'keyPrefix'>.
    • A locally declared wrapper that forwards its first parameter as the key to an already scoped
      translation function (e.g. const t = useCallback((key, opts) => tLocal(key, opts), [...]))
      inherits that function's namespace / keyPrefix.
  • fix: t() calls inside fenced code blocks (```) of doc comments are no longer extracted
    as real call sites.

v1.70.0

Compare Source

  • feat: improve namespace detection for t functions whose namespace is not a plain
    useTranslation('ns') literal (#​284):
    • useTranslation(ns ?? 'fallback') / useTranslation(ns || 'fallback') now resolve to the
      statically known side (the fallback literal when the left side is dynamic) instead of
      silently falling back to defaultNS.
    • TFunction<'ns'> / TFunction<'ns', 'keyPrefix'> is now honoured on destructured
      parameters as well (({ t }: { t: TFunction<'ns'> }), ({ t }: Props) with a local
      interface or type alias), not only on plain (t: TFunction<'ns'>) parameters.
      These previously caused status / extract to attribute such keys to the default namespace
      and report them as missing.

v1.69.2

Compare Source

  • fix: support the AST shape of @swc/core 1.16, which types function, arrow and method
    bodies as FunctionBody instead of BlockStatement (plain blocks like if (x) { … } are
    unchanged). Every "is this a function body?" check silently went false, which broke selector
    calls with a block body (t($ => { return $.a.b })), return-type inference from a function
    body (finite dynamic keys), and React component-boundary detection in the instrumenter — so
    useTranslation() / <Trans> were no longer injected. Both node types are now accepted.

v1.69.1

Compare Source

  • fix(lint): report hardcoded strings at the line where they actually occur. Line numbers were
    resolved by searching the raw source text, so a short string was reported at the first place
    it appeared as a substring anywhere in the file — e.g. <span>in</span> on line 4 was reported
    on line 1 because of import './settings.scss'. Lines are now taken from the AST node's span,
    falling back to the text search only when no span is available. This also fixes
    i18next-instrument-ignore / i18next-instrument-ignore-next-line being ignored for such
    strings, since the directives suppress issues by line
    (#​283).

Configuration

📅 Schedule: (in timezone UTC)

  • Branch creation
    • "before 7am"
  • Automerge
    • At any time (no schedule defined)

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

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • 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.

@openshift-ci
openshift-ci Bot requested review from dsimansk and pmeida August 18, 2026 00:05
@openshift-ci openshift-ci Bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Aug 18, 2026
@openshift-ci

openshift-ci Bot commented Aug 18, 2026

Copy link
Copy Markdown

Hi @red-hat-konflux-kflux-prd-rh02[bot]. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@red-hat-konflux-kflux-prd-rh02
red-hat-konflux-kflux-prd-rh02 Bot force-pushed the konflux/mintmaker/master/nodejs branch from 19a2ee5 to cb42ee8 Compare August 19, 2026 00:04
@red-hat-konflux-kflux-prd-rh02 red-hat-konflux-kflux-prd-rh02 Bot changed the title chore(deps): update dependency i18next-cli to v1.69.2 chore(deps): pin dependencies Aug 19, 2026
@red-hat-konflux-kflux-prd-rh02
red-hat-konflux-kflux-prd-rh02 Bot force-pushed the konflux/mintmaker/master/nodejs branch 2 times, most recently from 4876957 to c9c1bd8 Compare August 21, 2026 04:06
@twoGiants

Copy link
Copy Markdown

/ok-to-test

@openshift-ci openshift-ci Bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Aug 21, 2026
@twoGiants

Copy link
Copy Markdown

/approve
/lgtm

@openshift-ci openshift-ci Bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Aug 21, 2026
Signed-off-by: red-hat-konflux-kflux-prd-rh02 <190377777+red-hat-konflux-kflux-prd-rh02[bot]@users.noreply.github.com>
@red-hat-konflux-kflux-prd-rh02
red-hat-konflux-kflux-prd-rh02 Bot force-pushed the konflux/mintmaker/master/nodejs branch from c9c1bd8 to a3241bb Compare August 21, 2026 12:04
@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Aug 21, 2026
@openshift-ci

openshift-ci Bot commented Aug 21, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: twoGiants

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

The pull request process is described 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

@openshift-ci

openshift-ci Bot commented Aug 21, 2026

Copy link
Copy Markdown

@red-hat-konflux-kflux-prd-rh02[bot]: all tests passed!

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.

@twoGiants

Copy link
Copy Markdown

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 21, 2026
@openshift-merge-bot
openshift-merge-bot Bot merged commit d1d6cc7 into master Aug 21, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant