fix: publish only public packages in release workflow - #33
Merged
Conversation
Skip private packages (@codemcp/knowledge-core, @codemcp/knowledge-cli, @codemcp/knowledge-content-loader) during npm publish by using explicit --filter flags.
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.
Summary
@codemcp/knowledge-core,@codemcp/knowledge-cli,@codemcp/knowledge-content-loader) during npm publish--filterflags instead of attempting to publish all packagesProblem
The release workflow was trying to publish private packages (those marked with
"private": true), causing the npm publish step to fail withEPRIVATEerror.Solution
Changed from
cd packages/X && pnpm publishapproach topnpm --filter '@codemcp/package-name' publish, explicitly listing only the public packages to publish.