fix: use pnpm for npm publish in release workflow#480
Merged
Conversation
- Switch from npm to pnpm for consistent package manager usage - Add --no-git-checks flag for CI environment - Properly handle private packages in workspace 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
This was referenced Sep 8, 2025
Merged
Merged
Merged
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
This PR fixes the package publishing step in the release workflow by switching from npm to pnpm for consistency and proper workspace handling.
Problem
The release workflow was using
npm -r publishinstead ofpnpm -r publish, which caused several issues:honkit-rootis marked as"private": truein package.json, but npm's recursive publish doesn't properly respect workspace configurations--no-git-checksflag in CI environmentsSolution
Changed the publish command from:
To:
This ensures:
--no-git-checksflagTest Plan
N/A - This change affects the automated release workflow which runs when a Release PR is merged. The change will be validated when the next release is published.
🤖 Generated with Claude Code