How does pnpm's repo as a monorepo handle semantic release automation? Does it use semantic-release?

[205g0]

Pretty much the title...

[zkochan]

We use changesets: https://pnpm.io/using-changesets

[205g0]

Thanks for the hint. I played around a bit with changesets and how is your workflow (just for create the release docs, not the actual npm publishes)?

1. Development happens in branches which get pushed
2. Before they git merged you run a pnpx changeset version
3. Once merged on GH the changset action kicks in

But do you still trigger the changelog/release manually or is it done automatically?

[zkochan]

I do not run pnpx changeset version before merge. All the changeset files are merged to main. When I want to make a release, I run changeset version && pnpm install && pnpm publish -r on main branch.

[reuzel]

I'm using multi-semantic-release in my repository. All packages in my monorepo have version 0.0.0-development in the code base. Multi-semantic-release, based on commit history will assign the right version numbers and dependencies before publishing to my package repo. It does this smart: a package version will also be bumped if on of the dependencies updates.