Mark @emulators packages private - #18
Merged
Merged
Conversation
RhysSullivan
marked this pull request as ready for review
July 25, 2026 15:46
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
1 participant
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.
The @emulators npm scope belongs to a third party (vercel-release-bot/ctate), so our workspace packages under it can never be published there — every release-workflow attempt since 0.13.4 failed on them. They are bundled into @executor-js/emulate by tsup (noExternal) and referenced only via workspace protocol, so nothing resolves them from the registry.
Marks all 22 packages private: true (npm publish now refuses with EPRIVATE), drops their publishConfig, and removes the @emulators publish loop and version probe from the release workflow. @executor-js/emulate remains the single published artifact.