fix: allow access key expiration beyond current year - #201
Open
GatewayJ wants to merge 2 commits into
Open
Conversation
GatewayJ
force-pushed
the
agent/fix-access-key-expiration-date
branch
from
August 9, 2026 15:26
a92405e to
3825351
Compare
GatewayJ
marked this pull request as ready for review
August 9, 2026 15:39
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request
Description
Fix the shared date-time picker so access key expiration dates can navigate beyond the end of the current year.
react-day-pickerimplicitly limitscaptionLayout="dropdown"to the current year when no explicit end month is provided; using the month-only dropdown preserves month selection without introducing an arbitrary future limit.Add a regression test that renders the real DayPicker configuration at December 2026 and verifies that navigation to the next month remains enabled. The PR also retains the Next.js-generated
AGENTS.mdguidance refresh required by the repository.Type of Change
Testing
Manually verified navigation from August 2026 through January 2027, date selection in 2027, keyboard-accessible controls, and layout at desktop and 375px mobile widths with no console warnings or horizontal overflow.
Checklist
Related Issues
N/A
Screenshots (if applicable)
N/A — this changes calendar navigation behavior without changing visual styling.
Additional Notes
The full-repository Prettier check still reports the pre-existing, unchanged
components/object/tiff-viewer.tsxonorigin/main; both files changed by this fix pass Prettier.