Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(release): do not restart the daemon when skipLockFileUpdate is set #21389

Merged
merged 2 commits into from
Jan 29, 2024

Conversation

fahslaj
Copy link
Contributor

@fahslaj fahslaj commented Jan 29, 2024

Current Behavior

The daemon is always restarted after nx release version. Verbose logging is not propagated down to the nx release subcommands in the nx-release script.

Expected Behavior

The daemon is not restarted after nx release version if skipLockFileUpdate is set. Verbose logging is propagated down to the subcommands in the nx-release script.

Copy link

vercel bot commented Jan 29, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment
Name Status Preview Updated (UTC)
nx-dev ⬜️ Ignored (Inspect) Visit Preview Jan 29, 2024 5:28pm

@fahslaj fahslaj marked this pull request as ready for review January 29, 2024 18:51
@JamesHenry JamesHenry merged commit 69636ad into nrwl:master Jan 29, 2024
6 checks passed
@fahslaj fahslaj deleted the fix/skip-lock-file-update branch January 29, 2024 19:12
Copy link

github-actions bot commented Feb 4, 2024

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 4, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants