Does release-em generate separate release notes per directory in monorepo?

[markcellus]

@danderson00 This looks like a great package!

Before diving into using it, I was perusing the README to see if release-em generates separate individual release notes per package (that are in separate directories inside a monorepo). Other packages don't allow this so I was wondering if this one did. And if so, are the commit diffs scoped to just the directory? So if I make a commit that changes files in a package at the root directory, it won't affect the release notes in a package in a nested directory and vs?

I had opened cookpete/auto-changelog#136, which is a similar request in the auto-changelog repo but no luck there.

Thanks for any information you can provide.

[danderson00]

Hey Mark,

release-em simply runs release-it in each specified directory, so yeh, it should do. Having said this, I don't have any time to maintain this package at the moment. I should probably add some sort of notice in the readme!

Personally, I tend to use simple scripts to do this work these days and avoid the heavy handed approach of a full blown library. There are a couple of alternatives that seem to be gaining traction - release-it-yarn-workspaces seem pretty solid, and I was looking at oao a few days ago.

Hope this helps!

[markcellus]

Thanks for the reply! Hmmm those both seem to require yarn -- I don't use yarn, unfortunately. But I'll take a look at other alternatives since it sounds like the package may fall behind a bit. Thanks!

[danderson00]

Ahh, interesting, I didn't pick up on the fact you aren't using yarn. yarn workspaces definitely make working with a bunch of packages locally much easier. npm are following suit in v7 (according to their blog).

As an alternative, I'd be more than happy to hand this repo over if you think you could bend it to your needs. Looking at the code again, it might be a bit daunting to pick up - one of the big reasons I moved to shell scripts - simplicity!