chore(deps): update dependency @patternfly/react-table to v6.6.1

[red-hat-konflux]

This PR contains the following updates:

Package	Change	Age	Confidence
@patternfly/react-table (source)	6.6.0 → 6.6.1

---

Warning

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

---

Release Notes

patternfly/patternfly-react (@​patternfly/react-table)

v6.6.1

Compare Source

---

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 is behind base branch, 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]

⚠️ 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]

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: 6bdabe10-dd1e-4bcb-9e72-a33e7f2cfb3b

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]

Amber review

Status: Complete

Verdict

Assessment: COMMENT. This is a low-risk Renovate bump of the @patternfly/react-table peer dependency from 6.6.0 to 6.6.1 in the reusable gateway UI package, and it follows the repo's existing bot-update pattern. One consistency nuance and one cross-PR coordination point are worth a maintainer's attention before merge, but nothing here is blocking.

Findings

[Minor] Peer version bumped in isolation from the dev/lock version — the bump is effectively not exercised.
packages/gateway-management-ui/package.json L26 raises @patternfly/react-table to 6.6.1 under peerDependencies, but the same package still pins 6.6.0 under devDependencies (L38) and pnpm-lock.yaml still resolves 6.6.0 for both importer entries. As a result the package continues to be built and tested against 6.6.0 while advertising 6.6.1 to consumers, so the declared contract and the actually validated version diverge. This matches the shape of the repo's other Renovate peer-only bumps, so it is not new breakage, but it means the update has no real effect until the dev dependency and lockfile are advanced too. Confidence: High.

[Minor] @patternfly/* family drifts out of lockstep.
@patternfly/react-table@6.6.1 expects its sibling @patternfly/react-core / @patternfly/react-icons at the same version (the current lockfile shows react-table@6.6.0 pinned to react-core@6.6.0 and react-icons@6.6.0). After this change react-table is 6.6.1 while both siblings remain 6.6.0 (L24-L25), a mixed peer contract PatternFly recommends avoiding. See the Cross-PR coordination note below. Confidence: Medium.

Cross-PR coordination

Two other open dependency updates bump the sibling PatternFly packages to the same 6.6.1 target: one for @patternfly/react-core (#188) and one for @patternfly/react-icons (#189). Each of the three PRs advances exactly one @patternfly/* peer and leaves the other two at 6.6.0, so merging any one alone leaves the @patternfly/react-* family on mixed versions — which PatternFly expects to move in lockstep (the lockfile shows the 6.6.0 packages pinned to each other at the same version). Maintainers should decide to land #188, #189, and this PR together (or fold them into a single grouped update) and regenerate pnpm-lock.yaml once for the combined result, rather than merging them independently.

Findings Summary (ordered by severity, highest first)

1. [Minor] Peer bumped in isolation; devDependency + pnpm-lock.yaml still on 6.6.0, so the new version is not built/tested — Dependency consistency (package.json L26, L38)
2. [Minor] @patternfly/* family left on mixed 6.6.1/6.6.0 versions — Dependency consistency (package.json L24-L26)

Convention Checklist

Convention	Result
Conventional commit message	Pass
Dependency/version references consistent across manifest + lockfile	Fail

[jsell-rh]

Verdict

Assessment: COMMENT. This is a low-risk Renovate bump of the @patternfly/react-table peer dependency from 6.6.0 to 6.6.1 in the reusable gateway UI package, and it follows the repo's existing bot-update pattern. One consistency nuance and one cross-PR coordination point are worth a maintainer's attention before merge, but nothing here is blocking.

Findings

[Minor] Peer version bumped in isolation from the dev/lock version — the bump is effectively not exercised.
packages/gateway-management-ui/package.json L26 raises @patternfly/react-table to 6.6.1 under peerDependencies, but the same package still pins 6.6.0 under devDependencies (L38) and pnpm-lock.yaml still resolves 6.6.0 for both importer entries. As a result the package continues to be built and tested against 6.6.0 while advertising 6.6.1 to consumers, so the declared contract and the actually validated version diverge. This matches the shape of the repo's other Renovate peer-only bumps, so it is not new breakage, but it means the update has no real effect until the dev dependency and lockfile are advanced too. Confidence: High.

[Minor] @patternfly/* family drifts out of lockstep.
@patternfly/react-table@6.6.1 expects its sibling @patternfly/react-core / @patternfly/react-icons at the same version (the current lockfile shows react-table@6.6.0 pinned to react-core@6.6.0 and react-icons@6.6.0). After this change react-table is 6.6.1 while both siblings remain 6.6.0 (L24-L25), a mixed peer contract PatternFly recommends avoiding. See the Cross-PR coordination note below. Confidence: Medium.

Cross-PR coordination

Two other open dependency updates bump the sibling PatternFly packages to the same 6.6.1 target: one for @patternfly/react-core (#188) and one for @patternfly/react-icons (#189). Each of the three PRs advances exactly one @patternfly/* peer and leaves the other two at 6.6.0, so merging any one alone leaves the @patternfly/react-* family on mixed versions — which PatternFly expects to move in lockstep (the lockfile shows the 6.6.0 packages pinned to each other at the same version). Maintainers should decide to land #188, #189, and this PR together (or fold them into a single grouped update) and regenerate pnpm-lock.yaml once for the combined result, rather than merging them independently.

Findings Summary (ordered by severity, highest first)

1. [Minor] Peer bumped in isolation; devDependency + pnpm-lock.yaml still on 6.6.0, so the new version is not built/tested — Dependency consistency (package.json L26, L38)
2. [Minor] @patternfly/* family left on mixed 6.6.1/6.6.0 versions — Dependency consistency (package.json L24-L26)

Convention Checklist

Convention	Result
Conventional commit message	Pass
Dependency/version references consistent across manifest + lockfile	Fail

[jsell-rh]

The peer requirement is raised to 6.6.1 here, but devDependencies (line 38) and pnpm-lock.yaml still pin/resolve 6.6.0. So the package keeps building and testing against 6.6.0 while telling consumers to install 6.6.1 — the update is not actually exercised until the dev dependency and lockfile advance too. Also note react-table@6.6.1 expects its @patternfly/react-core/react-icons siblings (lines 24-25) at the same version; keeping them on 6.6.0 leaves the PatternFly family out of lockstep.