Post

Aaaaaand shipped!!!!! 🚢 🚀 🤩 bsky.app/profile/kent...

Testing out the example repo for the course. My favorite part of the log output of nx release is the inline diff of what's gonna change

Do you know what’s used to display the diff in the cli?

I'd need to dig in the code. @jameshenry.bsky.social would know

An interesting topic is automating migration versioning. When multiple people create migrations, they don’t always know the next package version but must set one in migrations.json. How can we manage package releases with dynamically bumped versions? 😊

Any idea what platform you'll use to release the course yet?

yep 😊. But more on that later 😅. It will be free though

How does publishing work with CI - when commits can happen faster than the build job, if the build job has unpredictably length? If there can be several commits being built and tested at the same time, possibly out of order, at what point does publishing happen?

Oh there has to be a "cut point". Like manually triggering a release pipeline, or running the release locally which assigns a tag, pushes it, but then the publishing to NPM (including NPM provenance) happens on CI 🙂. Something like that. I'll post here once that video is released :)

how you use verdaccio (if you still use this)

"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

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 🙂