Repository navigation
feat(hub)!: tool tarballs are published by a client script, never at hub boot (CL-8190) - #776
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
apps/hub/src/index.tsalready has no boot-time tool-registry publish path (CL-8112 removed the onboarding router; the file only importsCORBITS_TOOLS_REGISTRYfor read-back resolution, which stays).packages/onboarding/src/desired-state.ts'sreconcileTenantDesiredState, which packed and publishedworkspace-packtool pins viapublishCorbitsToolsRegistry. That call is removed: an absentworkspace-packpin now reportsblocked, same as any other operator-actionable gap, instead of packing.packages/onboarding/src/tenant-seed.ts's now-unusedToolRegistryPublishertype and its import are removed.scripts/publish-tools.tswas already the out-of-band API client this decision calls for (sign in, resolve tenant, pack withpackToolPackageTarball, PUT through the stock tarball route) — no change needed there.docs/seed-reconciliation.md,docs/local-rip.md) updated to state that nothing hub-triggered ever packs or publishes tool tarballs;bun run publish-toolsis the only publisher.Scope note
Item 4 (a
needs-converge/needs-list"tool packages missing" operator message inapps/web) is left for a follow-up:apps/web's client-driven converge loop (CL-8083) has no existing notion of tool-package pins or a registry-tarball read capability onStockHub, so surfacing this cleanly needs a newStockHubmethod plus wiring, which is out of scope for this bounded change.Test plan
bun run typecheckbun run lintbun run check:structuralbun --cwd apps/hub testbun --cwd apps/web testbun --cwd packages/onboarding testbun --cwd packages/tool-registry-publish test