fix(validations): use UTC year for streak/wrapped year validation upper bound

[nishupr]

Description

Fixes #6244

In lib/validations.ts, both streakParamsSchema and wrappedParamsSchema validate the year query parameter's upper bound using:

const currentYear = new Date().getFullYear();
return /^\d{4}$/.test(val) && yearNum >= 2008 && yearNum <= currentYear;

Problem with the old approach:

• new Date().getFullYear() returns the year in the server's local timezone, not UTC
• Near a year boundary (e.g. Dec 31 / Jan 1), this can cause inconsistent validation behavior depending on the server's local time offset from UTC
• This is the same class of inconsistency already addressed in app/api/wrapped/route.ts (bug: wrapped route calculates default year using server timezone instead of user's tz parameter #6242), where the default year calculation was changed to avoid server-local-time dependency

What this PR does:

• Replaces new Date().getFullYear() with new Date().getUTCFullYear() in both streakParamsSchema and wrappedParamsSchema validation refinements
• Updates the corresponding test file lib/validations.year.test.ts to compute CURRENT_YEAR via getUTCFullYear() for consistency, ensuring tests remain accurate regardless of the test runner's local timezone
• No change to the validation logic itself — only removes the server-timezone dependency

Note: The refine() callback only receives the field value, not other parsed fields like tz, so full per-user timezone-aware validation would require superRefine. Switching to UTC removes the core server-local-time dependency, which was the primary issue.

After:

const currentYear = new Date().getUTCFullYear();
return /^\d{4}$/.test(val) && yearNum >= 2008 && yearNum <= currentYear;

Pillar

• 🎨 Pillar 1 — New Theme Design
• 📐 Pillar 2 — Geometric SVG Improvement
• 🕐 Pillar 3 — Timezone Logic Optimization
• 🛠️ Other (Bug fix, refactoring, docs)

Visual Preview

No visual changes — this is a validation correctness fix.

Checklist before requesting a review:

• I have read the CONTRIBUTING.md file.
• I have tested these changes locally (localhost:3000/api/streak?user=YOUR_USERNAME).
• I have run npm run format and npm run lint locally and resolved all errors (CI will fail otherwise).
• My commits follow the Conventional Commits format (e.g., feat(themes): ..., fix(calculate): ...).
• I have updated README.md if I added a new theme or URL parameter.
• I have started the repo.
• I have made sure that i have only one commit to merge in this PR.
• The SVG output matches the CommitPulse "premium quality" aesthetic standard (no raw elements, smooth animations, correct fonts).
• (Recommended) I joined the CommitPulse Discord community for contributor discussions, mentorship, and faster PR support.

[vercel]

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

A member of the Team first needs to authorize it.

[github-actions]

📦 Next.js Bundle Size Report (Gzipped Sizes)

✨ No significant bundle size changes detected.

📊 Summary of Totals

Category	PR Size	Base Size	Difference
Total JS	3697.01 KB	3697.00 KB	+0.01 KB (+0.00%)
Total CSS	296.58 KB	296.58 KB	0 B

[Aamod-Dev]

Using getUTCFullYear() instead of getFullYear() in lib/validations.ts is a critical fix to ensure we don't have timezone-dependent validation failures around the New Year boundary. The update to lib/validations.year.test.ts to reflect this change is also perfectly executed. Approved!

[github-actions]

🎉 Congratulations @nishupr! 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! 💻✨