Pending
Generated artifacts
Run a free preview before connecting production publishing.
Generate preview
Free preview proves what Bloom can generate. This page shows what must be connected before Bloom can safely publish packages or host docs.
Production release paths stay gated behind owner approval, target-specific authorization, and dry-run evidence before anything reaches external systems.
Run a free preview before connecting production publishing.
Bloom needs GitHub authorization before it can open SDK, docs, config, or release pull requests.
TypeScript publishing should use package ownership checks, dry-run builds, install smoke tests, and approval before publish.
Python publishing should verify project ownership, build wheels/sdists, run install smoke tests, and publish only after approval.
Generate a docs preview before connecting repo or managed docs hosting.
Bloom will need to issue CNAME/TXT records, verify DNS, provision TLS, and keep previews noindexed until publish.
No registry publish, repo write, or docs cutover should happen without an explicit human approval step.