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.
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)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Adds
com.kingsrook.qbits:qbit-emailto the default G1 artifact allow-list andcom.kingsrook.qbits.email.apito the default allowed API packages (pom properties,GuardrailProjectfallbacks and README), the same treatment as qbit-object-storage. Only the publishedapipackage 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
SendMessageActionwith providerqbitEmail(additive core PR to follow) and need no qbit-email dependency at all.mvn verifygreen locally.🤖 Generated with Claude Code