fix(build): make Worker-safe connector package installable from Git - #337
Merged
Merged
Conversation
drewstone
marked this pull request as ready for review
September 29, 2026 04:23
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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.
Closes a real Builder launch blocker at its source
The maintained narrow OAuth/Hub/Sandbox exports exist, but consuming the exact source as a Git dependency failed during prepare: Node refuses to strip
tsdown.config.tsunder pnpm'snode_modules/.../store/...path. Retained original failure: Builder run 36512071660, artifact 11009570800.Use a native ESM
tsdown.config.mjs, with explicit JSDocUserConfigso declaration generation remains portable from nested paths. No new loader dependency, vendored connector, node_modules patch, install-policy bypass, or duplicate OAuth. Keep config checking with allowJs/checkJs and update the existing release fixture's filename.Exact final verification
Head
ce360e0f4f4ff37a30e8e92fa33c0edee61ead8e:No registry publication, provider call, deployment, or production credential use. Builder must adopt the narrow entrypoints and this exact package source or its later verified published release; merging this source alone does not fix a still-pinned broad consumer import.