feat(guardrails): allow qbit-email's published API by default #12

Merged
KofTwentyTwo merged 2 commits from feature/email-api-allowlist into main 2026-10-14 14:27:36 +00:00
KofTwentyTwo commented 2026-10-14 13:48:15 +00:00 (Migrated from github.com)

Adds com.kingsrook.qbits:qbit-email to the default G1 artifact allow-list and com.kingsrook.qbits.email.api to the default allowed API packages (pom properties, GuardrailProject fallbacks and README), the same treatment as qbit-object-storage. Only the published api package is allowed; qbit-email internals stay forbidden (package boundaries are exact).

Context: QRun-IO/qbit-marketing#13 (consumers import qbit-email internals today and carry temporary allow-lists). qbit-email's api package is QRun-IO/qbit-email (feature/public-api, PR to follow). After this parent is released, the five consumer qbits drop their per-repo allow-lists. Longer term, send-only consumers move to core SendMessageAction with provider qbitEmail (additive core PR to follow) and need no qbit-email dependency at all.

mvn verify green locally.

🤖 Generated with Claude Code

Adds `com.kingsrook.qbits:qbit-email` to the default G1 artifact allow-list and `com.kingsrook.qbits.email.api` to the default allowed API packages (pom properties, `GuardrailProject` fallbacks and README), the same treatment as qbit-object-storage. Only the published `api` package is allowed; qbit-email internals stay forbidden (package boundaries are exact). Context: QRun-IO/qbit-marketing#13 (consumers import qbit-email internals today and carry temporary allow-lists). qbit-email's api package is QRun-IO/qbit-email (feature/public-api, PR to follow). After this parent is released, the five consumer qbits drop their per-repo allow-lists. Longer term, send-only consumers move to core `SendMessageAction` with provider `qbitEmail` (additive core PR to follow) and need no qbit-email dependency at all. `mvn verify` green locally. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Sign in to join this conversation.