fix(date-range): compute the default range lazily to avoid a stale year

[Anexus5919]

Description

Fixes #4841

utils/dateRange.ts exposed the fallback range as a constant whose year was captured once at module load (new Date().getUTCFullYear() inside DEFAULT_DATE_RANGE). That value goes stale after a New Year rollover in a long-lived process, and formatDateRange returned it for missing or invalid years, inheriting the staleness.

This change replaces the constant with a lazy function getDefaultDateRange() that computes the current-year range each time it is called, so the value is always correct. formatDateRange now calls getDefaultDateRange() for its empty and invalid-year fallbacks. The DateRange interface was moved above the function it types.

DEFAULT_DATE_RANGE had no production callers (only the module and its test referenced it), so converting it to a function is safe. The test that read the old constant now calls getDefaultDateRange(), and a new test mocks the system clock across a year boundary (2030 then 2031) to confirm the range is computed lazily rather than captured once.

Pillar

• Pillar 1: New Theme Design
• Pillar 2: Geometric SVG Improvement
• Pillar 3: Timezone Logic Optimization
• Other (bug fix, refactoring, docs)

Visual Preview

Not applicable. Internal date-range utility change.

Checklist before requesting a review:

• I have read the CONTRIBUTING.md file.
• I have tested these changes locally (all utils/dateRange.test.ts tests pass, 14 tests including the new lazy-evaluation test; tsc --noEmit clean for this file).
• 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. (No 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. (Not applicable, utility change.)
• (Recommended) I joined the CommitPulse Discord community for contributor discussions, mentorship, and faster PR support.

[vercel]

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

A member of the Team first needs to authorize it.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[Aamod-Dev]

Great logical fix! Lazily computing the default date range prevents stale year bugs when the application instance runs across New Year's boundaries. Approving!

[Aamod-Dev]

Thanks for the PR. I've reviewed the changes and they look good to me.

I'm happy to approve this. Great job!

[Aamod-Dev]

Thanks for the contribution. I went through the changes and the overall approach looks good, but there are a few issues that should be addressed before this can be merged. Most of the concerns are related to correctness and maintainability.

• There are merge conflicts with the base branch. Please resolve them to ensure existing functionality isn't broken.

Once these issues are addressed, I'll be happy to take another look. Thanks again for the contribution.

[Anexus5919]

@Aamod007 @JhaSourav07
I have rebased this branch onto the latest main and resolved the merge conflict in utils/dateRange.ts.

Could you please take another look when you get a chance? Thanks!

[github-actions]

🚨 Hey @Anexus5919, 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]

Thanks for the contribution. The overall approach looks good, but the CI pipeline is currently failing. Please run the checks (like npm run format, npm run lint, and npm run test) locally to identify and fix the issues. Let me know once it's green!

[Anexus5919]

@Aamod007 Done. Please have a re-review on this. Thanks!

[Aamod-Dev]

Thanks for fixing the CI pipeline! Approving.

[github-actions]

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