Repository navigation
Provision deploys workflows only; tool registry publish stays at setup and boot (CL-7393) - #639
Merged
Merged
Conversation
Provision's tests asserted publishRootToolRegistry calls at sign-in and first-login creation for an unparented root bench. Those calls are the bug: publishCorbitsToolsRegistry runs the tool-package freshness check first, so a dirty packages/*/src under an unchanged version fails root first-login provisioning with tool_registry_publish_failed. Update the tests to assert no publish happens; provision deploys workflows only.
…CL-7393) publishRootToolRegistry ran publishCorbitsToolsRegistry, which checks tool-package freshness before publishing, at both first-login creation and every sign-in for a root (unparented) personal bench. A dirty packages/*/src under an unchanged version made that freshness check fail root first-login provisioning with tool_registry_publish_failed — a check meant to gate CI landed on the sign-in hot path instead. Delete both call sites and the publishToolRegistry hook entirely. Root-tenant tool registry publish now has exactly two callers: the workbench setup CLI and hub boot (apps/hub/src/system-seed.ts), which already publishes unconditionally and retries on failure rather than failing a sign-in.
Contributor
Author
Self-reviewVerdict: the change is correct and complete — provision no longer publishes the tool registry, hub boot and
Targeted tests: No defects found; nothing pushed. |
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.
Fixes CL-7393
Summary
packages/onboarding/src/provision.tscalledpublishRootToolRegistry(which runspublishCorbitsToolsRegistry, freshness check included) at first-login creation and on every sign-in for an unparented root personal bench. A dirtypackages/*/srcunder an unchanged version made that freshness check fail root first-login provisioning withtool_registry_publish_failed— a CI-gating check landing on the sign-in hot path.publishRootToolRegistryhelper, and thepublishToolRegistryhook onProvisionArgsentirely. Provision now only deploys the default workflow set; it never touches the tool registry.workbench setup(CLI) and hub boot (apps/hub/src/system-seed.ts), which already publishes unconditionally on every boot and retries (logs and lets the next boot retry) rather than failing sign-in.publishCorbitsToolsRegistry's own callers (setup/boot), never inline in provisioning.Manual check (documented per ticket, not automated — would require a full hub+DB e2e harness)
With a tool package's
src/edited and no version bump:bun run dev(hub boot) logs a tool-registry freshness/publish failure fromsystem-seed.tsand keeps running (retries next boot).tool_registry_publish_failed.Tests
bun test packages/onboarding/test/provision.test.ts— 18 pass.bun test packages/onboarding/test— 151 pass, 12 skip (DB-gated, noDATABASE_URLlocally).bunx tsc --noEmit -p packages/onboarding/tsconfig.json— clean.bunx eslint packages/onboarding/src/provision.ts packages/onboarding/test/provision.test.ts— clean.bun run scripts/checks/report-error.ts— 0 new findings.bun run scripts/checks/tool-package-freshness.ts,scripts/checks/browser-safe-subpaths.ts— ok.grep -rn publishRootToolRegistry packages/onboarding— no matches.Test plan