Post

Working on a course about versioning, changelog generation and releasing NPM packages with @nx.dev. This is the rough learning journey. What are you most interested in when it comes to releasing packages? I'll mostly focus on the releasing aspect, not necessarily package.json props etc

"Automate the release on CI" sounds like fun! I want to hear more. I actually like running (other release manager package) "nx run release --dry-run" locally, then without, then "git push --follow-tags" but I'm open for improvement and look for a reason to switch to "nx release" anyway 😂

cool. what are you using right now? And what's most tricky to figure out/challenging? Trying to see whether there's something I should cover

0 reposts0 likes

standard-version (deprecated) So far, no challenges since we wrote our entire release pipeline ourselves with custom scripts, mono-repo same-version policy etc. years ago Reasons to switch to nx release are getting rid of a deprecation and nx can do most of our scripts out of the box 🙂

I just got a new internal requirement that is maybe interesting for you: We decided to merge two mono-repos but don't want to immediately use the same version for both groups. E.g., one group continues with 7.x, the other one 2.x until the next major release were both go to 8.0