Skip to content

Publish corbits-tools at setup, not seed - #415

Merged
TheGreatAxios merged 7 commits into
mainfrom
cl-7071-publish-means-tarballs-live-on-a-tenant-99-the-bench
Aug 29, 2026
Merged

TheGreatAxios merged 7 commits into
mainfrom
cl-7071-publish-means-tarballs-live-on-a-tenant-99-the-bench

Conversation

@TheGreatAxios

Copy link
Copy Markdown
Contributor

Closes CL-7071.

Signup and seedTenant no longer pack tarballs from hub disk. workbench setup publishes the platform corbits-tools registry onto the root tenant once; descendant benches inherit it. Freshness (src/ moved, version did not) stays a publish/build failure, not a bench-create failure.

What changed

  • workbench setup publishes corbits-tools onto the created root tenant
  • seedTenant / signup deploy workflows only
  • Dirty packages/*/src without a version bump cannot abort minting a bench
  • @corbits/* still never falls through to npmjs

Why

Pack-from-hub-disk was a signup side effect that could abort a pending tenant. Interchange already walks ancestor registries; Workbench just needed to stop packing at seed.

Test plan

  • CLI setup/seed, hub-client seed, onboarding provision/credential/routes, freshness-check unit tests
  • CI bun run check

Signup and seedTenant must not pack tarballs. workbench setup publishes
the platform registry onto the root tenant; descendants inherit it.
Dirty src/ fails publish, not bench create.

CL-7071
workbench setup packs and publishes the platform toolbox onto the root
tenant. seedTenant deploys workflows only and inherits tarballs from
the ancestor registry. Freshness stays a publish/build failure.

CL-7071
Point local-dev, local-rip, seed-reconciliation, and CLI/publish
READMEs at workbench setup as the one-time registry publish.

CL-7071
@TheGreatAxios
TheGreatAxios force-pushed the cl-7071-publish-means-tarballs-live-on-a-tenant-99-the-bench branch 2 times, most recently from 74c4c82 to 8761d7e Compare August 29, 2026 14:29
@TheGreatAxios
TheGreatAxios merged commit 5136432 into main Aug 29, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant