fix: use pnpm to publish instead of lerna #2565
Merged
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
We need to use `pnpm publish` instead of `lerna publish` now that we're using catalogs, because pnpm is responsible for resolving the catalogs into real dependencies. This PR also bumps staking-sdk since the published version currently has unresolved catalog dependencies.
cprussin
force-pushed
the
cprussin/fix-publish-config
branch
from
ea6257f to
67e1021
Compare
mariobern
approved these changes
Apr 6, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We need to use
pnpm publishinstead oflerna publishnow that we're using catalogs, because pnpm is responsible for resolving the catalogs into real dependencies.This PR also bumps staking-sdk since the published version currently has unresolved catalog dependencies.