chore: simplify dryRun mode in release#1692
Merged
Merged
Conversation
🤖 GitHub commentsJust comment with:
|
trentm
previously approved these changes
Feb 6, 2026
Member
trentm
left a comment
There was a problem hiding this comment.
FWIW, I'd also be fine just not doing dry-run releases for every commit. Not really my repo though. :)
Member
Oh, looks like this is already only |
v1v
approved these changes
Feb 9, 2026
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
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.
Since #1651 the release process in
dryRunmode has had issues. The main reason is because we're usingverdaccioas a local registry to publish the packages locally and it does not support provenance neither trusted publishers.There has been some attempts to keep publishing locally in:
node-pupeteerimage for tests & fix release indry-runmode #1683but IMO these are workarounds to do something that is far from doing an actual release with lerna.
This PR tries to simplify by making the
dryRunmode behave like some CLI tools where they just print the list of actions that the command is going to do. In this case thedryRunmode is going to exec thelerna publishcommand in interactive mode and respond no when the command prompts for confirmation. Once canceled it will check in thestdoutif lerna detected the packages to be published.