fix(radio): change font size

[James-9696]

PR

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our Commit Message Guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:
  修改radio组件的字体大小

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

• Yes
• No

Other information

Summary by CodeRabbit

• Style
  • Increased radio component's default font size for improved readability and visual consistency.

[coderabbitai]

Walkthrough

The radio component's theme CSS custom property was updated to use the medium font size token instead of small, increasing the default font size from 12px to 14px for radio text styling.

Changes

Cohort / File(s)	Change Summary
Theme radio styles packages/theme/src/radio/vars.less	Updated CSS custom property for radio font size from small (12px / sm) to medium (14px / md) token

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A pixel grew today, from twelve to fourteen bright,
The radio text now stands with better might,
Medium size brings balance to the sight,
Harmony in styling, oh what a delight!

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The pull request title "fix(radio): change font size" accurately captures the main objective of the changeset. The title identifies the component being modified (radio), the type of change (fix), and the specific adjustment being made (font size). The change in the raw summary confirms the title's accuracy—the PR modifies the radio component's font size CSS custom property from a small size token (12px) to a medium size token (14px). The title is concise, specific, and follows conventional commit format, clearly conveying the primary change without unnecessary noise or vague terminology.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

packages/theme/src/radio/vars.less (1)

17-17: Document design change per PR requirements.

The PR checklist indicates tests and documentation were not added. For design/styling changes, consider adding:

1. Visual regression test or design snapshot to validate the new font size
2. Changelog entry or migration guide documenting the font size change
3. Any related component updates needed for consistency

This helps prevent regressions and communicates breaking changes to users.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4aec36d and 78feef3.

📒 Files selected for processing (1)

• packages/theme/src/radio/vars.less (1 hunks)

🔇 Additional comments (1)

packages/theme/src/radio/vars.less (1)

17-17: Verify design coordination and visual impact.

The font size increase from 12px to 14px affects all radio component text rendering. While the change uses the correct design token pattern, ensure this is aligned with your design system's intended updates and doesn't create visual inconsistencies across related components.

Please confirm:

1. Is this change part of a coordinated design system update?
2. Should similar font size adjustments be applied to other related components for visual consistency?
3. Are there visual regression tests or design snapshots that need updates?