Skip to content

chore(deps): update dependency react-intl to v10.1.22 - #226

Open
red-hat-konflux[bot] wants to merge 1 commit into
mainfrom
konflux/mintmaker/main/formatjs-monorepo
Open

chore(deps): update dependency react-intl to v10.1.22#226
red-hat-konflux[bot] wants to merge 1 commit into
mainfrom
konflux/mintmaker/main/formatjs-monorepo

Conversation

@red-hat-konflux

@red-hat-konflux red-hat-konflux Bot commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
react-intl (source) 10.1.18 → 10.1.22 age confidence

Warning

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

Release Notes

formatjs/formatjs (react-intl)

v10.1.22: react-intl: 10.1.22

Compare Source

10.1.22 (2026-08-16)

What's Changed

Full Changelog: https://github.com/formatjs/formatjs/compare/react-intl@10.1.21...react-intl@10.1.22

v10.1.20: react-intl: 10.1.20

Compare Source

10.1.20 (2026-08-02)

What's Changed

Full Changelog: https://github.com/formatjs/formatjs/compare/react-intl@10.1.19...react-intl@10.1.20

v10.1.19: react-intl: 10.1.19

Compare Source

10.1.19 (2026-07-30)

What's Changed

New Contributors

Full Changelog: https://github.com/formatjs/formatjs/compare/react-intl@10.1.18...react-intl@10.1.19

Dependencies

Configuration

📅 Schedule: (in timezone America/New_York)

  • Branch creation
    • Between 12:00 AM and 07:59 AM, only on Monday (* 0-7 * * 1)
  • 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.

@red-hat-konflux
chore(deps): update dependency react-intl to v10.1.22
bbc52bb 
Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
@red-hat-konflux

red-hat-konflux Bot commented Aug 31, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
[ERR_PNPM_UNSUPPORTED_ENGINE] Unsupported environment (bad pnpm and/or Node.js version)

Your Node version is incompatible with "/tmp/renovate/repos/github/openshift-online/hypershell".

Expected version: >=24.18.1
Got: v24.11.0

This is happening because the package's manifest has an engines.node field specified.
To fix this issue, install the required Node version.

@coderabbitai

coderabbitai Bot commented Aug 31, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 646cb612-dfad-4385-be64-00c20d8058c6

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

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

@jsell-rh

jsell-rh commented Aug 31, 2026 •
edited
Loading

Copy link
Copy Markdown
Collaborator

Amber review: changes requested

Amber review

Status: Complete

Verdict

REQUEST_CHANGES. This bot bump raises react-intl only in peerDependencies to 10.1.22, but the matching devDependencies entry and pnpm-lock.yaml are still pinned to 10.1.18, so the intended upgrade never actually takes effect and the manifest becomes self-inconsistent.

Summary

The change is a single-line dependency bump in packages/gateway-management-ui/package.json. There are no Go, security, reconciliation, or secret-handling concerns in scope; the one substantive issue is that the version bump is applied inconsistently across the package's dependency stanzas and lockfile.

Findings

[Major] Incomplete/inconsistent version bump (peer vs dev vs lockfile) — packages/gateway-management-ui/package.json:31

This package declares react-intl in two places, both exact-pinned:

  • peerDependencies.react-intl (line 31) — changed to 10.1.22
  • devDependencies.react-intl (line 57) — still 10.1.18

pnpm-lock.yaml (importer packages/gateway-management-ui, devDependencies.react-intl) also still resolves specifier: 10.1.18 / version: 10.1.18. Consequences:

  1. The library continues to be built and tested against 10.1.18 (the devDependency is what gets installed), so the advertised 10.1.22 support is never actually exercised — the bump does not achieve its stated goal.
  2. The package now declares an exact peer requirement of 10.1.22 that its own development environment (10.1.18) does not satisfy, producing an unmet-peer inconsistency for anyone building the package.
  3. The lockfile is left stale relative to package.json. (pnpm v9 --frozen-lockfile, used in lint.yml/e2e.yml/sdk-drift-check.yml/Makefile, does not record peer specifiers in the importer block, so it likely will not hard-fail on this alone — but the manifest and lockfile are nonetheless out of sync with the intended change.)

Fix: keep the two stanzas and the lockfile in sync — bump devDependencies.react-intl to 10.1.22 and regenerate pnpm-lock.yaml (pnpm install) in the same commit, or drop the change if the upgrade is not intended. Confidence: High on the inconsistency; Medium on whether CI hard-fails.

Cross-PR coordination

No material cross-PR coordination issue requires maintainer action.

Findings Summary (ordered by severity, highest first)

  1. [Major] react-intl bumped only in peerDependencies; devDependencies (L57) and pnpm-lock.yaml still pin 10.1.18, making the upgrade ineffective and the manifest self-inconsistent — Dependency Consistency (L31, L57)

Convention Checklist

Convention Result
Conventional commit message Pass
Dependency manifest / lockfile kept in sync Fail
Config separate from code Pass

jsell-rh
jsell-rh reviewed Aug 31, 2026
View reviewed changes

@jsell-rh jsell-rh left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verdict

REQUEST_CHANGES. This bot bump raises react-intl only in peerDependencies to 10.1.22, but the matching devDependencies entry and pnpm-lock.yaml are still pinned to 10.1.18, so the intended upgrade never actually takes effect and the manifest becomes self-inconsistent.

Summary

The change is a single-line dependency bump in packages/gateway-management-ui/package.json. There are no Go, security, reconciliation, or secret-handling concerns in scope; the one substantive issue is that the version bump is applied inconsistently across the package's dependency stanzas and lockfile.

Findings

[Major] Incomplete/inconsistent version bump (peer vs dev vs lockfile) — packages/gateway-management-ui/package.json:31

This package declares react-intl in two places, both exact-pinned:

  • peerDependencies.react-intl (line 31) — changed to 10.1.22
  • devDependencies.react-intl (line 57) — still 10.1.18

pnpm-lock.yaml (importer packages/gateway-management-ui, devDependencies.react-intl) also still resolves specifier: 10.1.18 / version: 10.1.18. Consequences:

  1. The library continues to be built and tested against 10.1.18 (the devDependency is what gets installed), so the advertised 10.1.22 support is never actually exercised — the bump does not achieve its stated goal.
  2. The package now declares an exact peer requirement of 10.1.22 that its own development environment (10.1.18) does not satisfy, producing an unmet-peer inconsistency for anyone building the package.
  3. The lockfile is left stale relative to package.json. (pnpm v9 --frozen-lockfile, used in lint.yml/e2e.yml/sdk-drift-check.yml/Makefile, does not record peer specifiers in the importer block, so it likely will not hard-fail on this alone — but the manifest and lockfile are nonetheless out of sync with the intended change.)

Fix: keep the two stanzas and the lockfile in sync — bump devDependencies.react-intl to 10.1.22 and regenerate pnpm-lock.yaml (pnpm install) in the same commit, or drop the change if the upgrade is not intended. Confidence: High on the inconsistency; Medium on whether CI hard-fails.

Cross-PR coordination

No material cross-PR coordination issue requires maintainer action.

Findings Summary (ordered by severity, highest first)

  1. [Major] react-intl bumped only in peerDependencies; devDependencies (L57) and pnpm-lock.yaml still pin 10.1.18, making the upgrade ineffective and the manifest self-inconsistent — Dependency Consistency (L31, L57)

Convention Checklist

Convention Result
Conventional commit message Pass
Dependency manifest / lockfile kept in sync Fail
Config separate from code Pass

Comment thread packages/gateway-management-ui/package.json
"react-dom": "19.2.8",
"react-hook-form": "7.82.0",
"react-intl": "10.1.18",
"react-intl": "10.1.22",

@jsell-rh jsell-rh Aug 31, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This bumps only the peerDependencies entry to 10.1.22. The devDependencies.react-intl (line 57) is still 10.1.18, and pnpm-lock.yaml (importer packages/gateway-management-ui) still resolves 10.1.18. Net effect: the library is still installed and tested against 10.1.18, so the upgrade is ineffective, and the package now declares an exact peer of 10.1.22 that its own dev environment does not satisfy. Please also bump the devDependency to 10.1.22 and regenerate the lockfile (pnpm install) in the same commit, or drop the change.

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

Reviewers

@jsell-rh jsell-rh jsell-rh left review comments

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@jsell-rh