bug: Align historical year ranges to user timezone offsets

[MasterJi27]

Resolves #5259. Aligns the query bounds from and to parameter values with timezone offset boundaries by converting local midnight and local end-of-day timestamps to UTC when fetching historical year contribution calendars.

[vercel]

@MasterJi27 is attempting to deploy a commit to the jhasourav07's projects Team on Vercel.

A member of the Team first needs to authorize it.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[github-actions]

🚨 Hey @MasterJi27, the CI Pipeline is failing on this PR and it has been marked as status:blocked.

Please fix the issues before this can be reviewed. Here's how:

1. Run checks locally before pushing:

npm run format:check   # Check Prettier formatting
npm run lint           # Run ESLint
npm run typecheck      # TypeScript type check
npm run test           # Run unit tests (Vitest)
npm run build          # Verify production build passes

2. Auto-fix common issues:

npm run format         # Auto-fix formatting with Prettier
npm run lint -- --fix  # Auto-fix lint errors where possible

3. Check the full failure log here:
👉 View CI Run

Once you push a fix and the CI passes, the status:blocked label will be removed automatically. 💪

[Aamod-Dev]

Great work! Timezone offsets are notoriously tricky to handle without heavy external libraries, but your use of Intl.DateTimeFormat to parse parts and calculate the offset milliseconds is very clever and lightweight.

The tests verifying the offset against Honolulu timezone perfectly validate the boundaries.

Labels Applied:

• level:intermediate: Timezone offset calculation using Intl parsing is moderately complex.
• type:bug: Fixes issue #5259 with year bounds.
• quality:clean: Clean, native implementation without adding heavy dependencies, and includes tests.
• gssoc:approved
• mentor:Aamod007

[MasterJi27]

Hi @sauravjha, @Aamod007 all required checks have passed and the PR has been approved. The remaining Vercel check appears to require team authorization. Could you please review and merge when convenient? Thanks

[github-actions]

🎉 Congratulations @MasterJi27! Your PR has been successfully merged. 🚀

Thank you for contributing to CommitPulse. Your work helps us build a better tool for the community.

⚠️ Important for GSSoC Contributors:
You are strictly advised to join our Discord Server as it is mandatory for all GSSoC participants. All important announcements, point claims, and community discussions happen there.

Keep building! 💻✨