chore: Migrate from npm to pnpm#134
Merged
kodiakhq[bot] merged 1 commit intomainfrom Mar 31, 2026
Merged
Conversation
erezrokah
changed the title
erezrokah
force-pushed
the
chore/switch-to-pnpm
branch
2 times, most recently
from
ed7502e to
a2984ca
Compare
marianogappa
approved these changes
Mar 31, 2026
- Replace package-lock.json with pnpm-lock.yaml - Set packageManager to pnpm@10.23.0 - Add minimumReleaseAge: 10080 (7 days) for supply chain protection - Update CI workflows for pnpm
erezrokah
force-pushed
the
chore/switch-to-pnpm
branch
from
a2984ca to
45c63c2
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.
Migrate from npm to pnpm for supply chain protection and org standardization.