chore(DataTable.Pagination): Convert DataTable.Pagination to CSS modules

[jonrohan]

This converts the DataTable.Pagination component to CSS modules. This was overlooked in the original migration.

Changelog

New

Changed

Converts styled-component styling to CSS modules.

Removed

Rollout strategy

• Patch release
• Minor release
• Major release; if selected, include a written rollout or migration plan
• None; if selected, include a brief description as to why

Testing & Reviewing

Merge checklist

• Added/updated tests
• Added/updated documentation
• Added/updated previews (Storybook)
• Changes are SSR compatible
• Tested in Chrome
• Tested in Firefox
• Tested in Safari
• Tested in Edge
• (GitHub staff only) Integration tests pass at github/github (Learn more about how to run integration tests)

[changeset-bot]

🦋 Changeset detected

Latest commit: 421bad1

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@primer/react	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

👋 Hi, this pull request contains changes to the source code that github/github depends on. If you are GitHub staff, we recommend testing these changes with github/github using the integration workflow. Thanks!

[github-actions]

size-limit report 📦

Path	Size
packages/react/dist/browser.esm.js	92.39 KB (-0.04% 🔽)
packages/react/dist/browser.umd.js	92.49 KB (-0.07% 🔽)

[primer-integration]

👋 Hi from github/github! Your integration PR is ready: https://github.com/github/github/pull/388357

[Copilot]

Pull Request Overview

This PR converts the styling of the DataTable.Pagination component (and the internal ButtonReset component) from styled-components to CSS modules.

• Replaces the styled-components-based ButtonReset with a functional component that applies a CSS module and clsx.
• Migrates all pagination-related styles in DataTable.Pagination to a CSS module, replacing StyledPagination and scoped class names.
• Adds a changeset entry for a minor release.

Reviewed Changes

Copilot reviewed 3 out of 5 changed files in this pull request and generated 1 comment.

File	Description
packages/react/src/internal/components/ButtonReset.tsx	Replaced styled-components with ButtonReset.module.css and a functional component.
packages/react/src/DataTable/Pagination.tsx	Swapped out StyledPagination and inline styles for Pagination.module.css + clsx.
.changeset/polite-pandas-tie.md	Added changeset marking the minor version bump for this chore.

Files not reviewed (2)

• packages/react/src/DataTable/Pagination.module.css: Language not supported
• packages/react/src/internal/components/ButtonReset.module.css: Language not supported

Comments suppressed due to low confidence (1)

packages/react/src/internal/components/ButtonReset.tsx:11

• Missing import of React for using React.PropsWithChildren and React.ButtonHTMLAttributes. Please add import type React from 'react' at the top.

}: React.PropsWithChildren & React.ButtonHTMLAttributes<HTMLButtonElement>) => {

[primer-integration]

🟢 golden-jobs completed with status success.

[joshblack]

Just one suggestion for the ButtonReset but otherwise LGTM 👍

[joshblack]

Completely separate from the refactor, would this be something we would ever want a container query for now that we can use them or is this best tied to the viewport range? (Was just curious)

[jonrohan]

Yes I think this was a bit verbose and would love either media query variables here or container queries.

[github-actions]

👋 Hi, there are new commits since the last successful integration test. We recommend running the integration workflow once more, unless you are sure the new changes do not affect github/github. Thanks!

[github-actions]

👋 Hi, there are new commits since the last successful integration test. We recommend running the integration workflow once more, unless you are sure the new changes do not affect github/github. Thanks!

[github-actions]

👋 Hi, there are new commits since the last successful integration test. We recommend running the integration workflow once more, unless you are sure the new changes do not affect github/github. Thanks!

[github-actions]

👋 Hi, there are new commits since the last successful integration test. We recommend running the integration workflow once more, unless you are sure the new changes do not affect github/github. Thanks!