Skip to content

OCPBUGS-86488: Bump to PatternFly 6.5.1#16491

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
logonoff:OCPBUGS-86488-pf-six-sevennn-actually-six-five
May 25, 2026
Merged

OCPBUGS-86488: Bump to PatternFly 6.5.1#16491
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
logonoff:OCPBUGS-86488-pf-six-sevennn-actually-six-five

Conversation

@logonoff
Copy link
Copy Markdown
Member

@logonoff logonoff commented May 25, 2026

Analysis / Root cause:

PF changed their package structure by accident - patternfly/patternfly#8428

Solution description:

Update PF CSS to 6.5.2 where they fixed the package structure

Test cases:

No special test cases required - just run CI

Summary by CodeRabbit

  • Chores
    • Updated PatternFly core, component, and design system library dependencies to newer stable versions for improved compatibility and support.
    • Simplified webpack build configuration.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 25, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@logonoff: This pull request references Jira Issue OCPBUGS-86488, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (5.0.0) matches configured target version for branch (5.0.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Analysis / Root cause:

PF changed their package structure by accident - patternfly/patternfly#8428

Solution description:

Update PF CSS to 6.5.2 where they fixed the package structure

Test cases:

No special test cases required - just run CI

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label May 25, 2026
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 25, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 5f849812-ef60-46ee-8845-023b4d21c916

📥 Commits

Reviewing files that changed from the base of the PR and between 6ba2a16 and af4a32b.

⛔ Files ignored due to path filters (1)
  • frontend/yarn.lock is excluded by !**/yarn.lock, !**/*.lock
📒 Files selected for processing (2)
  • frontend/package.json
  • frontend/webpack.config.ts
💤 Files with no reviewable changes (1)
  • frontend/webpack.config.ts

Walkthrough

PatternFly component library versions are updated across multiple packages to newer patch and minor versions, and the webpack configuration is adjusted by removing a resolve alias entry that is no longer needed.

Changes

PatternFly Dependency Update

Layer / File(s) Summary
PatternFly version updates
frontend/package.json
Multiple @patternfly/* packages are bumped to newer versions: @patternfly/patternfly, @patternfly/react-charts, @patternfly/react-code-editor, @patternfly/react-core, @patternfly/react-drag-drop, @patternfly/react-icons, @patternfly/react-styles, @patternfly/react-table, @patternfly/react-templates, and @patternfly/react-tokens move from ~6.5.0/~6.4.x/~8.5.0 series to ~6.5.1/~6.5.2/~8.5.1 series.
Webpack resolve alias adjustment
frontend/webpack.config.ts
The webpack resolve.alias entry for @patternfly/patternfly pointing to a specific dist path is removed; other alias entries for prettier modules remain in place.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 11 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'OCPBUGS-86488: Bump to PatternFly 6.5.1' is related to the changeset but incomplete; the PR updates PatternFly dependencies to 6.5.2, not 6.5.1, and removes a webpack alias, making it partially inaccurate. Clarify the title to reflect the actual target version (6.5.2) and consider mentioning the webpack alias removal if significant, or keep focused on the primary dependency update.
✅ Passed checks (11 passed)
Check name Status Explanation
Description check ✅ Passed The PR description includes root cause analysis and solution description but is missing several required template sections: Screenshots, Test setup, Browser conformance, and Reviewers/assignees.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.
Stable And Deterministic Test Names ✅ Passed This PR only updates PatternFly dependencies in frontend config files. No test files or test names are modified, so this check is not applicable.
Test Structure And Quality ✅ Passed PR contains no Ginkgo test code changes - only updates PatternFly dependencies in frontend/package.json and removes a webpack alias. The custom check is not applicable to this PR.
Microshift Test Compatibility ✅ Passed No Ginkgo e2e tests are added in this PR. Changes are limited to frontend/package.json (dependency versions) and frontend/webpack.config.ts (webpack config). Check is not applicable.
Single Node Openshift (Sno) Test Compatibility ✅ Passed No new Ginkgo e2e tests added; PR only updates PatternFly frontend dependencies and webpack config, so SNO compatibility check does not apply.
Topology-Aware Scheduling Compatibility ✅ Passed PR only modifies frontend package.json and webpack.config.ts; no deployment manifests, operator code, or controllers. Topology-aware scheduling check does not apply.
Ote Binary Stdout Contract ✅ Passed PR modifies only frontend files (package.json and webpack.config.ts) for PatternFly dependency updates; no changes to Go code, test binaries, or process-level stdout writing.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed This PR does not add any Ginkgo e2e tests; it only updates frontend PatternFly dependencies and webpack configuration. The IPv6/disconnected network check is not applicable.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

@logonoff
Copy link
Copy Markdown
Member Author

/verified by CI

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label May 25, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@logonoff: This PR has been marked as verified by CI.

Details

In response to this:

/verified by CI

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@logonoff: This pull request references Jira Issue OCPBUGS-86488, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (5.0.0) matches configured target version for branch (5.0.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
Details

In response to this:

Analysis / Root cause:

PF changed their package structure by accident - patternfly/patternfly#8428

Solution description:

Update PF CSS to 6.5.2 where they fixed the package structure

Test cases:

No special test cases required - just run CI

Summary by CodeRabbit

  • Chores
  • Updated PatternFly core, component, and design system library dependencies to newer stable versions for improved compatibility and support.
  • Simplified webpack build configuration.

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci Bot requested review from sg00dwin and stefanonardo May 25, 2026 16:42
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 25, 2026
resolve: {
extensions: ['.ts', '.tsx', '.js', '.jsx'],
alias: {
'@patternfly/patternfly': path.resolve(__dirname, 'node_modules/@patternfly/patternfly/dist'),
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

😆

@vojtechszocs
Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label May 25, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 25, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: logonoff, vojtechszocs

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
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 25, 2026

@logonoff: 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.

@openshift-merge-bot openshift-merge-bot Bot merged commit fa9c81b into openshift:main May 25, 2026
9 checks passed
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@logonoff: Jira Issue Verification Checks: Jira Issue OCPBUGS-86488
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-86488 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

Analysis / Root cause:

PF changed their package structure by accident - patternfly/patternfly#8428

Solution description:

Update PF CSS to 6.5.2 where they fixed the package structure

Test cases:

No special test cases required - just run CI

Summary by CodeRabbit

  • Chores
  • Updated PatternFly core, component, and design system library dependencies to newer stable versions for improved compatibility and support.
  • Simplified webpack build configuration.

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 openshift-eng/jira-lifecycle-plugin repository.

@logonoff logonoff deleted the OCPBUGS-86488-pf-six-sevennn-actually-six-five branch May 25, 2026 19:41
@openshift-merge-robot
Copy link
Copy Markdown
Contributor

Fix included in release 5.0.0-0.nightly-2026-05-26-050719

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. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants