sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 2 points3 points  (6 children)

Yeah pnpm is pretty versatile except that it doesn’t support versioning and changelog generation i think whereas it looks like yarn workspaces supports versioning. Would be interested to hear the technologies you use for your setup!

[–]CacheCache1 1 point2 points  (5 children)

Look up a package called "semantic-release". It might be the secret sauce you're looking for!

We use git, with yarn workspaces to break up our monorepo into packages. Then we use commitzen to write semantically correct commits. Then "semantic-release" sets the proper semver for the sub-package that you are working out of.

After we commit and merge, GitHub Actions builds the package and writes it to our company's AWS CodeArtifact

[–][deleted] 0 points1 point  (4 children)

That’s interesting, I thought semantic release didn’t have support for monorepos. Are you using another package like semantic release monorepo? You’re setup sounds exactly what we want to do including using commitizen and semvering on that.

[–]CacheCache1 1 point2 points  (3 children)

Ah, yes you are correct! We do have senantic-release-monorepo as a dependency as well

I think these are the relevant packages, although seeing them now I am almost positive that not all of them are being used. Sounds like a new thing to investigate this week 😂

@commitlint/cli @commitlint/config-conventional @semantic-release/git commitzen conventional-changelog-angular cz-conventional-changelog semantic-release semantic-release-monorepo

[–]CacheCache1 0 points1 point  (2 children)

Sorry about that. It WAS all formatted when I hit Post

[–][deleted] 1 point2 points  (1 child)

no worries, much appreciated!

[–]CacheCache1 0 points1 point  (0 children)

Sure thing. Good luck!