Release highlights

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/patternfly (changelog)

  • @patternfly/patternfly@6.0.0

• patternfly/patternfly-react (changelog)

  • @patternfly/react-charts@8.0.0
  • @patternfly/react-code-editor@6.0.0
  • @patternfly/react-core@6.0.0
  • @patternfly/react-icons@6.0.0
  • @patternfly/react-styles@6.0.0
  • @patternfly/react-table@6.0.0
  • @patternfly/react-tokens@6.0.0

• PatternFly extensions

  • @patternfly/react-catalog-view-extension@6.0.0 (changelog)

  • @patternfly/react-console@6.0.0 (changelog)

  • @patternfly/react-log-viewer@6.0.0 (changelog)

  • @patternfly/react-topology@6.0.1 (changelog)

  • @patternfly/react-user-feedback@6.0.0 (changelog)

  • @patternfly/react-virtualized-extension@6.0.0 (changelog)

  • @patternfly/quickstarts@6.0.0 (changelog)

  • @patternfly/virtual-assistant@2.0.2 (changelog)

  • @patternfly/react-component-groups@6.0.0 (changelog)

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:

• About PatternFly AI
• AI guidelines
• Chatbot
• Conversation design

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

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:

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
  • Added validation support and a new validated prop. We also added a text input group with validation example.
• Tile
  • Deprecated the tile component in favor of card. For usage information, refer to the cards as tiles example.

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.

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.

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.

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

• Added a new status and severity pattern, which provides guidance for using our new severity icons.
• Updated our quick starts extension with more content guidance.
• Documented our tabular number modifier .pf-v6-m-tabular-nums in typography, numerics, and table.
• Added guidance for editorial styling to our content component (formerly called text content).
• We've started updating images across our design guidelines to represent PatternFly 6 styling.

• Shortened component descriptions shown in component page headers and on the all components page.
• Added more details about React tokens and how to migrate them.
• Added React example documentation for text input group.

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.

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.

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

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:

• All tokens pages:
  • About tokens
  • All PatternFly tokens
  • Develop with tokens
  • Design with tokens
  • Note: Any @patternfly/react-tokens referencing global variables will need to be updated, since global variables have been replaced with tokens. Following our token migration instructions will help you determine the correct token to use.
• Our design foundations
  • Colors
  • Icons
  • Spacers
  • Typography

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

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.

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.

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

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.

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.