fix: prevent publishing unresolved workspace imports - #1577
Merged
Conversation
Size Report
Startup median (7 runs, lower is better):
Top changed chunks: no changes in the largest emitted chunks. |
|
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
@agent-device/*workspace imports from escaping the npm bundleprepackimmediately when the built JS or declarations retain a private workspace importagent-device devices --jsonfrom the globally installed tarball in package CIdeps.alwaysBundleAPIThis fixes the published 0.20.4 regression where
npx agent-device devicesfailed with an unresolved@agent-device/ad-scriptimport. The build had warned about unresolved workspace packages but still emitted a publishable tarball.Validation
npx --yes agent-device@0.20.4 devicesagent-device devices --jsonsucceedspnpm check:unit— 597 files / 5261 tests plus smoke passedpnpm checkunder load and passed in isolation in 340 msDocs
No docs or skills changes: this restores the existing packaged CLI contract and adds release-integrity enforcement; command behavior is unchanged.