Update outdated dependencies

[thatblindgeye]

Replacement for #9127 (comment), the following are deps that need major bumps only; renovate will handle any minor bumps.

• @dnd-kit/modifiers - Current: 7.0.0 | Latest: 9.0.0 | Depended by: react-drag-drop@npm:@patternfly/react-drag-drop@6.2.0-prerelease.16 - chore(deps): update dependency @dnd-kit/modifiers to ^9.0.0 and @dnd-kit/sortable to ^10.0.0 #11580

• @dnd-kit/sortable - Current: 8.0.0 | Latest: 10.0.0 | Depended by: react-drag-drop@npm:@patternfly/react-drag-drop@6.2.0-prerelease.16 - chore(deps): update dependency @dnd-kit/modifiers to ^9.0.0 and @dnd-kit/sortable to ^10.0.0 #11580

• @octokit/rest - Current: 20.1.1 | Latest: 21.1.0 | Depended by: patternfly-react - chore(deps): update dependency @octokit/rest to ^21.1.0 #11601

• @rollup/plugin-commonjs | Current: 26.0.3 | Latest: 28.0.2 | Depended by: patternfly-react - chore(deps): update dependency @rollup #11626 (review)

• @rollup/plugin-node-resolve - Current: 15.3.1 | Latest: 16.0.0 | Depended by: patternfly-react - chore(deps): update dependency @rollup #11626 (review)

• @rollup/plugin-replace - Current: 5.0.7 | Latest: 6.0.2 | Depended by: patternfly-react - chore(deps): update dependency @rollup #11626 (review)

• case-anything - Current: 2.1.13 | Latest: 3.1.0 | Depended by: react-core@npm:@patternfly/react-core@6.2.0-prerelease.15 - chore(deps): update dependency case-anything to ^3.1.0 #11595

• concurrently - Curent: 8.2.2 | Latest: 9.1.2 | Depended by: patternfly-react - chore(deps): update dependency concurrently to ^9.1.2 #11584

• cypress - Current: 8.7.0 | Latest: 14.0.1 | Depended by: eact-integration@npm:@patternfly/react-integration@6.0.0-prerelease.22 - chore(deps): update dependency cypress to ^14.0.1 #11625

• eslint-config-prettier - Current: 9.1.0 | Latest: 10.0.1 | Depended by: patternfly-react - chore(deps): updated dependency eslint-config-prettier to ^10.0.1 #11630

• eslint-plugin-react-hooks - Current: 4.6.2 | Latest: 5.1.0 | Depended by: patternfly-react - chore(deps): updated dependency eslint-plugin-react-hooks to ^5.1.0 #11632

• eslint-plugin-testing-library - Current: 6.5.0 | Latest: 7.1.1 | Depended by: patternfly-react - chore(deps): updated dependency eslint-plugin-testing-library to ^7.1.1 #11631

• glob - Current: 10.4.5 | Latest: 11.0.1 | Depended by: patternfly-react - chore(deps): update dependency glob to ^11.0.1 #11596

• rimraf - Current: 5.0.10 | Latest: 6.0.1 | Depended by: patternfly-react - chore(deps): update dependency rimraf to ^6.0.1 #11597

• typescript-eslint - Current: 7.18.0 | Latest: 8.22.0 | Depended by: patternfly-react - chore(deps): update dependency typescript-eslint to ^8.22.0 #11600

• vite - Current: 5.4.14 | Latest: 6.0.11 | Depended by: demo-app-ts@6.0 - chore(deps): update dependency vite to ^6.0.11 #11604

Note that react-router will be handled by #11172, and the React upgrades will be handled by #11371 (none of these deps are listed above)

---

Jira Issue: PF-1149

[Mash707]

Hi @thatblindgeye I would like to work on this. I haven't worked much with upgrading dependencies in a large project.
I looked up previous PRs which involved updating dependecies. From what I understand is that we require to updates the versions in yarn.lock and package.json. Could you provide more information regarding this if possible?
Also Do I need to create separate PR for each dependency upgrade?
Thank You.

[thatblindgeye]

@Mash707 Mainly updating versions in the package.json and building locally (this should update the yarn.lock automatically). Outside of that it could require resolving any errors that occur from upgrading -- though depending on the errors that may mean we have to wait until our next breaking change release to upgrade.

A separate PR would be good just in case there are issues that need to be resolved -- again depending on that it can be easier to review more PRs that are smaller in size than a huge single PR. That said grouping similar deps together would be fine, i.e. a single PR for both the dnd-kit upgrades needed.

That said if it feels overwhelming at all and you'd like to work on other issues in our react repo (outside the a11y ones you've picked up, which awesome job for taking those on) we can try to find some issues that might be a good fit (some of our issues might be goof first issues, we just haven't applied the label to them).

[Mash707]

@Mash707 Mainly updating versions in the package.json and building locally (this should update the yarn.lock automatically). Outside of that it could require resolving any errors that occur from upgrading -- though depending on the errors that may mean we have to wait until our next breaking change release to upgrade.

I'll try updating some packages and see how things go.

That said if it feels overwhelming at all and you'd like to work on other issues in our react repo (outside the a11y ones you've picked up, which awesome job for taking those on) we can try to find some issues that might be a good fit (some of our issues might be goof first issues, we just haven't applied the label to them).

I am currently exploring small issues which I happen to understand. It would be great help if you guys can help me figure issues on which I can work. I did join the mailing list to look out for upcoming community meetings.
Thank You !!!