Austin Fahsl

@ZeroJsus When `useWorkspaces` is set to `true` in lerna.json, all dependencies will be installed to `node_modules` at the root. This is a [yarn workspaces](https://classic.yarnpkg.com/lang/en/docs/workspaces/) pattern. If you need to have...

This appears to be working in the latest (v7.1.4) as well. I am closing this issue, but feel free to open another one if anyone continues to experience problems on...

Yes, @comp615 is correct. The --no-git-reset option just ensures that the files changed during the publish action are not reset. It is not intended to function as a way to...

To all it may concern, this PR is being closed for clarity since Lerna already supports the `workspace:` protocol. It was added a while ago as part of the `pnpm`...

@Nokel81 it is documented as an argument for `lerna version`, which are all valid arguments for `lerna publish` also when performing both steps with just a single `lerna publish` command....

@MikolajMGT thank you for opening this issue. The intention is that the `package.json` and `lerna.json` files for the workspace reside at the root of the workspace, with all packages contained...

@MikolajMGT thank you for providing clarity. I see how this solution could solve some problems in the situation you have provided. Why is the `lerna.json` file in a component directory...

Hey everyone! This has been fixed with this PR - https://github.com/nrwl/nx/pull/22304 Now, `nx release` will use the root `.npmrc` when publishing. This includes support for scoped registries and auth within...

> @fahslaj could you perhaps provide some insight in the recommended approach here? > > It feels like the `nx release` feature currently doesn't support a pretty standard publishing workflow:...

@lorenzodejong I am glad you were able to make it work with that script! As for the potential bug, if you could create a specific report with repro steps that...