Consolidate dependabot dependency updates

[alexanderpaolini]

Why

I wasn't seeing any movement from the dependabot PRs, so I consolidated them into this one. Will bug people until we can merge it.

What

Closes: #500
Closes: #499
Closes: #498
Closes: #497
Closes: #494
Closes: #488

• Updates ip-address to 10.4.0.
• Updates Better Auth to 1.6.22.
• Updates PostCSS to 8.5.23.
• Updates Next.js to 16.2.11 across all consumers.
• Synchronizes eslint-config-next with Next.js 16.2.11.
• Updates Sharp to 0.35.3.
• Pins react-analyzer to its existing codeload commit URL so lockfile regeneration remains CI-installable.
• Regenerates pnpm-lock.yaml with the repository-pinned pnpm version.

Test Plan

• pnpm install --frozen-lockfile
• pnpm verify:push
  • Formatting passed.
  • Lint passed with existing warnings and no errors.
  • All 29 typecheck tasks passed.
• pnpm build
  • All 17 build tasks passed
• Auth, Cron, and TK targeted suites: 53 tests passed.
• Sharp 0.35.3 runtime smoke test successfully generated a PNG.

Checklist

• Database: No schema changes, OR I ran pnpm db:generate and committed the generated files in packages/db/drizzle/
• Environment Variables: No environment variables changed, OR I have contacted the Development Lead to modify them on Coolify BEFORE merging.

[coderabbitai]

Warning

Review limit reached

@alexanderpaolini, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 45 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro Plus

Run ID: 1dd70144-a94f-4827-8c73-051e3f9285d0

📥 Commits

Reviewing files that changed from the base of the PR and between 3f4205e and 92034b6.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml, !pnpm-lock.yaml

📒 Files selected for processing (12)

• apps/2025/package.json
• apps/blade/package.json
• apps/bloomknights/package.json
• apps/club/package.json
• apps/cron/package.json
• apps/gemiknights/package.json
• apps/guild/package.json
• apps/khix/package.json
• apps/tk/package.json
• package.json
• packages/auth/package.json
• tooling/tailwind/package.json

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}