Declare publish config for npm provenance

[gentamura]

Summary

• mark each package as public with npm provenance enabled so trusted publishing works

Testing

• not run (metadata change only)

Summary by CodeRabbit

• Chores
  • Updated package publishing configuration across multiple packages to enable public distribution and provenance metadata tracking.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Four package.json files across the monorepo receive identical publishConfig objects, specifying public access and provenance metadata for npm publishing. No functional code changes.

Changes

Cohort / File(s)	Summary
PublishConfig additions packages/api/package.json, packages/auth/package.json, packages/db/package.json, packages/types/package.json	Added publishConfig field with access: "public" and provenance: true to enable public npm package publishing with provenance metadata

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

Hop, hop—the packages now shine bright,
Public access set just right! 📦✨
With provenance marks in place,
The registry's a trusty space,
Four repos bundled, pure delight! 🐰

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/add-publish-config

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between aaebf21 and dab3d29.

📒 Files selected for processing (4)

• packages/api/package.json (1 hunks)
• packages/auth/package.json (1 hunks)
• packages/db/package.json (1 hunks)
• packages/types/package.json (1 hunks)

---

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 and usage tips.}