pf-org-version-update

To update PatternFly package versions for a new release, you resolve versions from explicit input or by scanning the repository, then apply them across root, documentation-site, and documentation-framework package.json files. It updates devDependencies, resolutions, and peerDependencies.

When adding a new PatternFly release entry in versions.json, it inserts a new top release, marks the previous latest as hidden, and ensures all releases maintain a consistent versions map with all required packages.

The best way to validate PatternFly version updates locally is to run install, build, serve, and generate screenshots. It provides a verified workflow with steps to ensure changes are correct before finalizing the release.

Yes, you can automate resolving @patternfly/* dependencies by letting the skill scan the repository via an included script. This produces a complete set of @patternfly/* versions without requiring explicit user input for every package.

No, the PatternFly version update process touches only PatternFly packages. It updates dependencies across root package.json, documentation-site, and documentation-framework peerDependencies while leaving non-PatternFly packages untouched.

You need to update peerDependencies in the documentation-framework to ensure compatibility with the new PatternFly release. It updates these alongside root devDependencies and resolutions to maintain version consistency across the repository.