fix: NPM publishing with workspaces (#1714) - #1715
Merged
aklenik merged 1 commit intoOct 1, 2025
Merged
Conversation
aklenik
force-pushed
the
fix-1714-npm-publish-workspace
branch
from
October 1, 2025 07:43
d7304d4 to
b3a5c8e
Compare
* tell the npm config command explicitly that it does not operate with workspaces * set root package to private to prevent accidental publishing of monorepo * updated git repo naming format in package.json files * remove generator-caliper from integration test and publishing, pending removal of package itself Signed-off-by: Attila Klenik <a.klenik@gmail.com>
aklenik
force-pushed
the
fix-1714-npm-publish-workspace
branch
from
October 1, 2025 07:44
b3a5c8e to
af0b3d8
Compare
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
2 participants
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 #1714