Skip to content

fix: should include maxValue year in CalendarYearPicker range#10149

Merged
LFDanLu merged 1 commit into
adobe:mainfrom
chirokas:fix-10140
Jun 3, 2026
Merged

fix: should include maxValue year in CalendarYearPicker range#10149
LFDanLu merged 1 commit into
adobe:mainfrom
chirokas:fix-10140

Conversation

@chirokas
Copy link
Copy Markdown
Contributor

@chirokas chirokas commented Jun 2, 2026

Closes #10140

✅ Pull Request Checklist:

  • Included link to corresponding React Spectrum GitHub Issue.
  • Added/updated unit tests and storybook for this change (for new code or code which already has tests).
  • Filled out test instructions.
  • Updated documentation (if it already exists for this component).
  • Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

🧢 Your Project:

@chirokas chirokas marked this pull request as ready for review June 2, 2026 13:26
Copy link
Copy Markdown
Member

@LFDanLu LFDanLu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, verified it locally as well. Thanks for the fix!

@LFDanLu LFDanLu added this pull request to the merge queue Jun 3, 2026
Merged via the queue into adobe:main with commit 457647b Jun 3, 2026
29 checks passed
@chirokas chirokas deleted the fix-10140 branch June 3, 2026 09:17
@yihuiliao yihuiliao added the no testing Does not require manual testing during testing session label Jun 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no testing Does not require manual testing during testing session ready for review small review Easy to review PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CalendaryYearPicker max date last year cut off

3 participants