David Sveningsson

I noticed this myself, if someone could give me some pointers I could create a pull request fixing this.

I would like this to be merged too, I'm kind of strict but I don't want to have a warning about unsatisfied peer dependencies: > npm WARN [email protected] requires a...

Of course, but that puts a burden on me to keep it up-to-date with updates, security advisories, etc. So in practice I don't think I'd be doing anyone a favor...

Being hit by this issue as well. In general I'm not very fond of the approach used by this plugin as essentially having two builds takes twice the time, twice...

I've run into this as well. In my case I'm stuck at semantic-release trying to verify the git permissions (similar to #1271). I don't want to add the necessary credentials...

> Looking to see if people are still interested in this endeavour of supporting monorepos for semantic release? I've seen some third party packages try and support but we haven't...

Author of the `conventionalcommits` preset PR here, I wasn't aware there was a specification. I can create a PR to add it to the schema and specification if you want?

Sorry for the late reply, the notifications got lost in my mailbox. Is this issue not that `@semantic-release/git` is not configured to add and commit `package-lock.json`?

Interesting, not sure what causes this. I'm running this with NPM workspaces myself and there is even an integration test covering this scenario: https://github.com/ext/semantic-release-lerna/blob/master/test/integration.test.js#L271 Can you show the full log?

To me it seems like `package-lock.json` is already modified before starting `semantic-release`. Can you run `git diff` before running semantic-release? Do you run `npm ci` or `npm install`?