chore(security): bumps nodemailer 8→9 et better-auth 1.6.23

[Tbeaumont79]

Suite du durcissement sécu (#24). Deux mises à jour de dépendances, chacune testée.

nodemailer 8.0.10 → 9.0.3

Corrige GHSA-p6gq-j5cr-w38f (l'option raw contournait disableFileAccess/disableUrlAccess → lecture fichier / SSRF). Notre mailer.ts n'utilise que l'API SMTP basique (inchangée en v9) ; le seul breaking change v9 (validation TLS stricte sur requêtes sortantes) ne nous concerne pas.

• ✅ nodemailer absent de pnpm audit
• ✅ sendMail v9 accepte notre forme d'appel (test jsonTransport)

better-auth 1.6.15 → 1.6.23

8 patchs sécu/bugfix de la lib d'auth, même mineure, aucune migration de schéma.

• ✅ Login testé end-to-end : magic-link → verify (302 + cookie session) → appel authentifié /api/billing/summary (200)

Validation

pnpm install --frozen-lockfile OK · typecheck OK · 124/124 tests verts.

🤖 Generated with Claude Code

[netlify]

✅ Deploy Preview for monumental-speculoos-a69398 ready!

Name	Link
🔨 Latest commit	72305a9
🔍 Latest deploy log	https://app.netlify.com/projects/monumental-speculoos-a69398/deploys/6a467dd5f13cd700082c319e
😎 Deploy Preview	https://deploy-preview-25--monumental-speculoos-a69398.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 44 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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: defaults

Review profile: CHILL

Plan: Pro

Run ID: 8e9911b4-bb99-41fd-9528-8ac5c1b85c52

📥 Commits

Reviewing files that changed from the base of the PR and between cf6ef8f and 72305a9.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

• apps/app/package.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/dep-bumps-security

---

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.}