Skip to content

Release highlights

PatternFly 6.3

For the Q3 2025 PatternFly release, we completed our initiative to support React 19 across PatternFly and made significant progress towards finalizing our component animations. We also added new ChatBot features, new CLI guidelines, and updated docs for our AI principles and motion guidelines. Updates for these key areas can be found here, in this quarter's release highlights.

The following packages were promoted with this release. Outside of our primary initiatives for this release, we addressed reported bugs and continued to enhance PatternFly with new features, as detailed in the linked changelogs.

React 19 support

PatternFly now includes support for React 19 across all components and extensions, enabling you to benefit from new React features and performance enhancements.

This update is non-breaking, and PatternFly 6 will continue to support React 17 and 18 in line with our support policy. In future releases, we plan to more fully leverage React 19's capabilities to enhance existing PatternFly features and introduce new ones.

Component animations

As we progress in our effort to integrate motion design across PatternFly components, we added the following new animations in this release. To provide a holistic view of our animated components, we also put together an interactive animations demo, which we will continue to update as we add additional animation support.

Note: Browsers may slow down or deactivate animations on resource-intensive pages. This can occur when continuous animations (like multiple spinners) are active at the same time as other demanding tasks (like frequent data polling), which can overload the browser's processing capacity.

enable-animations codemods

We have also created an enable-animations codemod, which adds the hasAnimations prop to components that require opt-in animations.

Keep in mind that, depending on your codebase, this codemod could introduce breaking changes that require further attention. In particular, when you run the codemod you will be asked whether you want to opt into animations for table components, or just for the react-core package.

To enable the optional animations run the following command:

npx @patternfly/pf-codemods --only enable-animations /path-to-src

Expansion

We added expansion animations that apply a fade-in and slide-in transition as hidden content sections are expanded in a variety of components. A similar, reversed animation applies when expanded sections are collapsed.

The following list highlights opt-in requirements and links to examples. Unless an animation is marked with "Requires opt-in," it will be enabled by default.

  • Accordion

    • Example: All accordions in our examples and demos.

  • Dual list selector with tree

  • Expandable section

  • Form

  • Navigation

    • Example: Expandable navigation examples.
    • Note: This animation was introduced in our 6.2 release, but performance issues were reported. For this release, we reworked the animation to resolve these issues.

  • Search input

  • Tree view

    • Requires opt-in.
    • Example: All tree view examples and demos, which have opted in.

  • Table (in beta)

    • Requires opt-in.

    • Example: Expandable table and compound expandable table, which have both opted in.

    • Notes:

      • This release does not include expansion animations for tree tables.

      • To prevent possible visual issues with expandable and compound expandable tables, ensure that your implementation aligns with our currently recommended structure. In your table's code:

        • <Table> must have isExpandable passed to it.

        • Any <Tbody> containing expandable rows must have isExpanded logic.

        • Any <Tr> that acts as a "control row" (for normal expandable tables) or has the isControlRow prop (for compound expansion tables) must have isContentExpanded logic. This logic should match the isExpanded logic being passed to other sub-components.

        • Any <Tr> that expands/collapses and contains the expandable content must have isExpanded logic (this should always have been the case in order for expansion to work).

        • Any <Td> within an expandable <Tr> must wrap any content in an ExpandableRowContent.

        • The basic structure, which is used in our expandable and compound expandable examples should resemble this:

          <Table isExpandable> // if opting into animations, pass the hasAnimations prop or run the enable-animations codemods to auto-apply the prop ...Thead content... <Tbody isExpanded={...logic for checking for expansion...}> <Tr isContentExpanded={...logic for checking for expansion...}> // for compound expandable, pass isControlRow as well ..."control row" content... </Tr> <Tr isExpanded={...logic for checking for expansion...}> <Td> <ExpandableRowContent> ...the content to display for the cell... </ExpandableRowContent> </Td> </Tr> </Tbody> </Table>

Feedback

The following components contain animations that give users dynamic feedback, helping to communicate that an action has taken or will take place.

  1. Buttons

    • Animation: When a button is clicked, the active state color ripples outward from the center of the button.
    • Example: All buttons in our components, including in our button examples and demos.

  2. Helper text validation

    • Animation: When an error occurs in an input that supports helper text (such as in the form and progress components), the helper text fades in as danger styles are applied.
    • Example: The static text and dynamic status example for helper text.

  3. Form validation

  4. Menu toggle validation

  5. Progress

    • Animation: When an error occurs in a progress bar, the component "jiggles" from side to side as danger styles are applied.
    • Example: The "Danger variant" option in our progress helper text example.

  6. Tabs

    • Requires opt-in for HTML-only implementations.
    • Animation: The bottom "active tab" line slides between tabs as they are selected.
    • Example: All default tabs in our examples and demos. This animation does not apply to boxed tabs.
    • Note: To avoid a breaking change, this animation is opt-in for HTML-only implementations. To support this, view our HTML guidance for animating the tab accent mark.
Icons

The following animations are unique to each icon and don't support any custom icons. For example, you cannot apply the favorite animation to any icon besides the favorite star.

  1. Favorite

    • Animation: When a favorite button is clicked, the star "pulses" and fills with color.
    • Example: All favorite buttons in our examples and demos, including our animated favorite button example.

  2. Hamburger menu

    • Animation: The middle bar of the hamburger icon transforms into an arrow to indicate whether the menu will expand or collapse when clicked. The behavior differs slightly for desktop and mobile views:
      • Desktop: Both arrows appears on hover or keyboard focus as appropriate.
      • Mobile: When the menu is expanded, a "collapse" arrow is displayed. When collapsed, an "expand" arrow appears on hover or focus.
    • Example: All hamburger menu buttons in our examples and demos, including our page examples.
    • Note: This animation automatically occurs for hamburger menu buttons in mastheads, but not elsewhere. You can view implementation details in the hamburger button example, which demonstrate how to set up the animation logic outside of mastheads.

  3. Settings

    • Animation: When a settings button or menu toggle receives hover or keyboard focus, the cog rotates. When focus is lost, it rotates back to its original position.
    • Example: All settings buttons and menu toggles in our examples and demos, including our animated settings button example.

PatternFly AI

We updated our high-level AI principles and guidelines to expand guidance and improve the usability of this resource. We integrated community feedback and research to include new patterns and recommendations that have emerged from the increased use of AI features in products. As the design and implementation of AI features continue to evolve, so will this guiding resource.

ChatBot

We expanded our ChatBot extension with improvements identified in a recent usability study, including editable messages and compact styles. We also added other requested features, such as auto-scrolling for messages (a community contribution!), empty and error states for the chat history drawer, and expandable code blocks—to name a few.

On the documentation side, there's a new "Customizing messages" guide that provides guidance for using rehype plugins for advanced HTML customization.

We also fixed reported bugs, which require no updates on your end.

CLI experience guidelines

With the help of a community contribution, we now have a CLI handbook that offers guidance for designing command-line interface experiences. This resource outlines unique accessibility considerations for CLIs, as well as writing guidelines for crafting well-designed messages, documentation, and interactive CLI experiences.

Motion guidelines

We updated our motion guidelines to bring our docs up to date with our new component animations, document motion patterns we're using, and expand the motion development guide with additional details and instruction.

What's next?

For the Q4 release of PatternFly, we look forward to sharing updates on our design guidelines audit, system-wide accessibility improvements, new extensions, and more. We'll share the next round of exciting news in a few months!

PatternFly 6.2

For the Q2 2025 PatternFly release we made progress in a few of our key initiatives, including PatternFly 6 migration enablement, component animations, React 19 support, and the continued evolution of PatternFly AI. Updates for these key areas can be found here, in this quarter's release highlights.

The following packages were promoted with this release. Outside of our primary initiatives for this release, we addressed reported bugs and continued to enhance PatternFly with new features, as detailed in the linked changelogs.

PatternFly 6 enablement

As products have continued their PatternFly 6 migration journeys, we've received helpful feedback on the upgrade process, including common roadblocks and situations that could use more guidance. So, we expanded and reorganized the PatternFly 6 upgrade guide to more clearly and comprehensively support the upgrade process.

Component animations

Our highly-anticipated animations project focuses on integrating motion design into PatternFly components, to enhance user experiences and provide additional cues for interaction. You can keep track of this project via our micro-animations roadmap.

Note that animations will either be specified as opt-in or opt-out:

  • Opt-in: Requires additional updates to your codebase in order to function properly. These could cause test failures, depending on how your testing is set up, so you must manually opt into these animations and configure them appropriately.
  • Opt-out: Turned on by default. To disable these animations, work with the PatternFly team to find a solution.

With this release, 3 components now support animations:

  1. Alert
    • Animation type: Opt-in.
    • Animation: For alerts within a group, there's a slide-in animation as new alerts are received and a slide-out animation as alerts are dismissed.
    • Example: To visualize the motion, you can interact with our website examples, which have opted in to animations.
    • Note: By default, alert animations are opt-in and will only apply to alerts within an alert group. Opting into animations could require test updates. To ensure your test pass, the quickest solution is to set hasAnimations to false. Additionally, when alerts are dynamically added to a group, you must ensure that new alerts are prepended to the alert group list, rather than appended to the end of it.
  2. Navigation
    • Animation type: Opt-out.
    • Animation: For expandable navigation items, the sub-menu fades in and out as navigation items are expanded and collapsed.
    • Example: As an opt-out animation, you can see this motion by default across expandable navigation items.
  3. Notification badge
    • Animation type: Opt-in.
    • Animation: When the animation is triggered (for example, when a new notification arrives), the bell icon has a "ring" animation.
    • Example: To illustrate the motion of this animation, we added a notification badge "With animations" example.

React 19 support

We’ve made significant progress towards React 19 support in PatternFly, which is being tracked in the React 19 roadmap. Our remaining work involves updating our React dependencies, testing version support, and creating any necessary support resources or documentation.

PatternFly AI

In the world of PatternFly AI, we've continued our focus on expanding our ChatBot extension. As more Flyers have used ChatBot, we've gained insight into the types of new features that would have the most impact. To make progress on growing ChatBot needs, this release adds many new features, including an inline drawer display mode, the ability for users to give message feedback, support for quick starts, additional content types for messages, and much more.

To see a complete list of new ChatBot features, view the changelog.

Along with these new features, we've updated our documentation:

Expanded chart library

PatternFly has historically provided a charting solution using the Victory chart library. With this release, PatternFly is also now delivering 2 charts based on the Apache ECharts library, including a line chart and a Sankey chart.

Additionally, EChart is now listed as a peer dependency for PatternFly. To use these new chart solutions, add 'echart' to your project dependencies and follow PatternFly's documentation to build out your charts.

Notable changes

Outside of our key initiatives, there are a few notable changes that may require changes to your codebase and tests.

Components

  • Button

    • Change: The aria-disabled will now only render when true, not on elements where it is false or undefined.
    • Required update: Update tests that either:
      • Check for aria-disabled to be false
      • Match the disabled property

  • Charts

    • Change: Errors related to Victory 37.3.4 have been addressed.
    • Required update: If you're using PatternFly 5, use react-charts v7.4.8 with Victory v37.3.4 or later.

  • Table

    • Change: The column management and column management with draggable features have been rewritten to replace the use of the deprecated <DragDrop> component.
    • Required update: Remove the deprecated <DragDrop> component by referring to the updated table demos.

Extensions

  • ChatBot
    • Change: DOMpurify is no longer a dependency.
    • Required update: Uninstall/remove DOMpurify from your codebases.
  • ChatBot
    • Change: <MessageBar> is now a PatternFly <TextArea>, which leads to the following type changes for <MessageBarProps>:
      • onChange:
        • Before: (event: React.ChangeEvent<HTMLDivElement>, value: string) => void;
        • After: (event: React.ChangeEvent<HTMLTextAreaElement>, value: string | number) => void;
      • onSendMessage:
        • Before: (message: string) => void;
        • After: (message: string | number) => void;
    • Required update: Where relevant, update the Typescript types for <MessageBarProps>.
  • Quick starts
    • Change: The markdown parser has been changed to one that's more actively being maintained.
    • Required update: Verify that any custom markdown extensions you use still work properly. This is where bugs are most likely from this change.
      • If you see issues with custom markdown extensions, or any other issues with markdown parsing after this change, please raise an issue.

What's next?

For the Q3 release of PatternFly, we will continue to focus on the initiatives mentioned in this release, fix bugs, and address any new, critical priorities that come up. To stay up to date with our primary focus areas, you can keep track of the PatternFly Roadmap initiatives board.

PatternFly 6.1.1

Extension updates

As a quick follow up to our last release, this update publishes the new data view extension.

PatternFly 6.1

Component updates

We fixed bugs that were reported in our components, the details of which can be found in the patternfly-react release notes and the patternfly (Core) release notes.

These changes mostly resolved functionality issues and made improvements to visual styles.

The following fix could require manual updates depending on how you handle breakpoints in your code:

  • We fixed a breakpoint issue in our table component, which caused table breakpoints for the desktop/mobile responsive layout to be 1px off from our other component breakpoints. Now, the table will responsively update between desktop and mobile at the same width as our other components. If you've manually configured your own breakpoints to match table's previous breakpoints, this fix will require you to make CSS updates to bring your code in line with the updated breakpoint value.

Website updates

  • We fixed an issue on PatternFly.org that prevented proper page loading when navigating to new pages via in-content links.

  • We updated the PatternFly.org accessibility scorecard and will begin to resolve accessibility violations that were identified.

Content updates

  • We updated design guideline images for context selector to align with PatternFly 6 styles. There is an ongoing effort to update images across PatternFly.org to reflect our new visuals, tracked in this PatternFly 6 design guidelines issue.
  • We updated the illustrations on the component overview page.
  • We updated and added "draggable" examples to dual list selector and data list.
  • We updated our ChatBot documentation:
    • We renamed the extension to "ChatBot", to better brand our offering and help distinguish it from other general "chatbot" features.
    • We combined and organized our documentation into a few cohesive pages: "Overview", "UI", and "Messages". Note that our documentation structure could continue to change as our extension grows. We will continue to share updates when changes occur.
    • We moved our basic and embedded ChatBot demos to the "Overview" page for better visibility.
    • We added initial ChatBot design guidelines, which can also be found on the "Overview" page.
    • We added documentation for new features, as described in the following section.

Extension updates

ChatBot

We've continued to evolve our new ChatBot:

Component groups

  • We added customization support to error state via PatternFly empty state props, including a custom icon and title heading level.

PatternFly 6.0

The official release of PatternFly 6 is here! It contains all of the previous features from our alpha and beta releases, but also adds everything described in these release highlights.

PatternFly AI

We're excited to introduce PatternFly AI: our new effort to support and integrate AI into our design system. We've added guidance and resources, contained within a new section of our website:

As with all things AI currently, this area will continue to grow and mature with time.

Component groups restructuring

We made many updates to our component groups extension to improve accuracy, usability, and alignment with PatternFly 6. We've moved its website section to our top-level navigation for better visibility, and also to support necessary sub-navigation. We've conceptually grouped the components into functional categories. Additionally, we renamed some of the components to be more accurate.

Our updated documentation includes:

*Category-
*Components-
Content containers
- Details page
- Multi-content card
- Page header (previously named "content header")
- Service card (new!)
Controls
- Bulk select
- Close button
- Responsive actions (new!)
Error communication
- Error boundary
- Error state
- Missing page (previously named "invalid object")
- Unauthorized access (previously named "not authorized")
- Unavailable content
- Warning modal
Helpers
- Column management modal
- Log snippet
- Shortcut grid
Status and state indicators
- Ansible
- Severity (previously Battery)
- Skeleton table
- Status (new!)
- Tag count

React component updates

Here are the most significant updates we made to our React components:

  • Data list
    • Refactored <DataListCheck> to use <Checkbox> internally, which fixes broken checkboxes in the examples.
  • Dropdown
    • Added focusTimeoutDelay, which specifies the time to wait before setting focus on the first dropdown item when shouldFocusFirstItemOnOpen is set.
    • Fixed issues with invalid and jumpy scrolling when focusing on the first menu item.
  • Jump links
    • Fixed improper offset in demo.
  • Menu toggle
    • Removed pf-m-actions and, consequently, SplitButtonOptions. Items should now be passed directly to splitButtonItems.
    • Added isPlaceholder to support customizable placeholder text, as well as a corresponding example.
  • Text input group
  • Tile

Token updates

Design tokens

We updated existing design tokens and added new tokens to support directional box-shadows. To see these tokens, search "box-shadow" in our tokens documentation.

We also added a few new tokens to support the needs of our new chatbot, including:

  • A tertiary background token that accommodates containers placed on a secondary background.
  • Inverse hover and inverse clicked tokens.

React tokens

To address instances where design tokens and CSS variables for charts unintentionally created identical React tokens, we added a t_ prefix to all design token references in our React tokens. This makes it easier to differentiate between design tokens and CSS variables.

Extensions maintenance

We made a couple of updates to ensure that extensions are in line with PatternFly 6 styling:

  • Updated card title style in quick starts to maintain the proper blue link style.
  • Updated link catalog tiles in the catalog view extension to be actionable cards.

Content updates

In addition to the previously mentioned documentation updates, we've made changes to the following content areas:

Design guidelines

Miscellaneous cleanup and enhancements

PatternFly 6 beta

We’re excited to share the next milestone in our journey to PatternFly 6–our beta release! This beta introduces more improvements and refinement, and contains all major PatternFly 6 features.

Your continued participation, support, and feedback will help ensure that PatternFly 6 is as well-tested and bug-free as possible before the full release.

Design updates

Rem units

We updated our sizing system to be based on rems, instead of pixels. Rems are relative units that adjust font size based on a webpage's HTML document root element size. For example, if the root size is 10px, a rem size of 1.5 would be 15px. This allows you to scale your font sizes, based on a root size of your choice. PatternFly's default root element size is 16px.

Motion framework

We created a framework for micro animation CSS tokens, which will be used to enable component animations in future minor releases.

Content updates

We made more improvements to our website docs, to ensure that they're accurate and inline with our new token system. A variety of pages and sections were updated, including:

Component updates

We promoted some of our beta and "next" components to become standard components in PatternFly 6. These will be fully-supported features going forward:

  • Buttons with count label
  • Editable labels
  • Flyout and drilldown menus and navigation
  • Menu toggle with status indicator
  • Modal title with status indicator
  • Inline spinners
  • Timestamp component

We updated some of our components to make room for additional features, including:

  • Multiple page body elements within the page component.
  • Icons in navigation items.

We also made updates to some of our component structure and naming conventions. We:

  • Renamed the "text" component to "content."
    • Added <hr> element support to the content component.
  • Refactored pagination to use menu toggle rather than options menu.
  • Updated the <ToolbarItem> variant prop options:
    • Replaced "chip-group" with "label-group", to align with the deprecation of chip.
    • (Previously) Removed "bulk-select", "overflow-menu", and "search-filter" variants for <ToolbarItem>.
  • Restructured the masthead component:
    • Renamed <MastheadBrand> to <MastheadLogo>
    • Renamed <MastheadMain> to <MastheadBrand>
    • Wrapped <MastheadToggle> and <MastheadBrand> in <MastheadMain>
    • Updated our documentation to align with the new structure.
  • Restructured the empty state component:
    • Made it less composable, in order to address styling issues.
    • Updated <EmptyStateHeader> and <EmptyStateIcon> to be rendered internally within <EmptyState>. They should now only be customized using props.
    • Updated the content passed to the icon prop on <EmptyState> to be wrapped by <EmptyStateIcon> automatically.
    • Made the titleText prop required.

We made some updates to react-charts.

  • In order to support multiple chart libraries, Victory based charts have moved to a "victory" directory.
  • Victory is now an optional peer dependency, allowing future chart libraries to be installed without including Victory dependencies and vice versa
    • You may choose to install the single "victory" package to cover all features
    • Or, install packages based on the features used in your app (e.g., "victory-core", "victory-tooltip", etc.).

Extension updates

We applied PatternFly 6 styles to the rest of our extensions. All have now been upgraded to use the PatternFly 6 beta:

  • Topology
  • Component groups
  • React console
  • Log viewer
  • User feedback
  • Catalog view
  • Quickstarts

Related design resources can also be found in our PatternFly 6 Figma kit.

Bug fixes

We fixed bugs that were reported throughout the alpha period including. We:

  • Fixed an issue with displaying card hover/click states in the user feedback extension.
  • Updated buttons to support wrappers, which fixes padding issues.
  • Updated our documentation to replace terms from deprecated components. For example, replacing "chip" with "label" across React property names.
  • Fixed various small accessibility bugs.
  • Removed deprecated or unused properties across some of our components.

PatternFly 6 alpha

We're excited to announce that our alpha release of PatternFly 6 is now live. Here are the highlights that you should know about!

PatternFly 6 visual theme

As you've probably already noticed on the alpha website: PatternFly 6 has a new look. Our brand new visual theme is more modern and refined, so that you can create UIs that are more seamless and lightweight.

All of our components have a new look to match. As you use the alpha website, take a look at our component examples, demos, and patterns to explore our redesign.

Design tokens

In order to support PatternFly 6, and any future visual theming capabilities, we have implemented a design token system for PatternFly. For more details and instructions on how to use tokens, you can refer to our new design token documentation.

Our tokens cover both dark and light themes, and make it easier to support both in your product. We also updated our dark theme handbook to align with our tokens.

*Note:- The PatternFly 5 design library is not built with tokens. To take advantage of our token system, you must upgrade your product to PatternFly 6.


Edit this page on GitHub
Red Hat
Copyright © 2014-2025 Red Hat, Inc.
Privacy statementTerms of useAll policies and guidelines