fix: increase RateLimiter maxSize to prevent IP eviction (#5893)

[vipul674]

Fixes #5893

Problem

RateLimiter was instantiated with maxSize=1, allowing only one IP to be tracked at a time. When a new IP made a request, the previous IP's entry was evicted, effectively disabling rate limiting for all users except the most recent one.

Fix

Increased maxSize from 1 to 10_000 in both ci-analytics and pr-insights route rate limiters, matching the default used elsewhere in the codebase.

[vercel]

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

A member of the Team first needs to authorize it.

[vipul674]

@JhaSourav07 Ready for review.

[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	3628.47 KB	3628.47 KB	0 B
Total CSS	284.92 KB	284.92 KB	0 B

[vipul674]

@JhaSourav07 Review Reminder

[Aamod007]

Difficulty: beginner – Increases RateLimiter maxSize from 1 to 10,000 in ci-analytics and pr-insights routes to prevent IP eviction.

Quality: clean – Simple config fix.

Type: bug – Fixes issue #5893, prevents premature IP eviction.

Good fix!

[github-actions]

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