Releasing Nx Release

[@ankushkalia6982]

Thanks for bringing this in NX. It was really a missing essential tool in NX. However I have a question about it. Your demo shows a synchronised release but we use nx in our monorepo where we have multiple apps which have their own libs and shared libs across apps. These apps are being managed by different teams as per their own release cycle. So how can I configure the nx release that will help me release individual apps and version them independently. It is a very common use case I assume for nx. An example on this would really help where you can have multiple thin apps with their own libs and shared libs and still we are able to release.

[@0xSLN]

I'd really appreciate this as well. Lots of companies that are warming up to monorepos see package independence as essential.

[@nazarshvets7501]

Yea, I have a really great example, where in my FE monorepo we have application and pdf library. And we publish this pdf library as separate package with its own versioning, so backend devs can integrate this documents to render them as files. And we also use this package in our FE application to show previews (render in react-pdf viewer) Now we are managing versioning manually, but it would be really great to have that separation build in nx itself

[@rand0mtv660]

Please check out the docs linked in the description because the presenter mentions near the end that individual package releases are documented as well.

[@nelsond6]

​@@rand0mtv660I must be blind as I can't find anything that mentions running these commands for individual projects.

[@JohanVrolix]

How do I configure my GitHub username to be included when using nx release?

[@sander-s]

I’m already happy with my custom release executor: npx nx affected -target=release. Easy peasy. Nx is so flexible ❤

[@EdititStudio]

Will it work after merge? I want my CI to release (and version) all the affected packages after a branch is merged to dev

[@lordpelo]

Is there an "official way" to do on demand releases? I mean release just 1 or a couple of apps/libs instead of the whole monorepo?

[@ebichu8126]

Any possible way to integrate with Jira?

[@Jebarpg]

Thank you for everything in this video. Will gitmoji commitizen and commitlint be considered for adaptation in the commit type selection and scope selection work flow? I feel this might be something as you said for the community to implement, but was just curious if these were on nx teams radar.

[@piotrczech2653]

Great video! I have a question regarding programmatically reading the version number without publishing. You demonstrated a method to access the version directly without referencing the package.json using `await releaseVersion`. Is there a way to read the current compiled `releaseVersion` into my application, possibly displayed in the footer? I discovered the genversion package as a solution, but I'm curious to know how others address this challenge.

[@NoviceNestTrader]

For some reason when I add the scope to the commit the release command not generating a new version e.g "fix(scope): something to be committed"

[@damiant12345]

I have an question, why did you removed libs file structure in new nx monorepo?

[@rahulaggarwal9867]

Hi, thanks for this helpful video, we are using Nx in for a huge mono-repo and want to use Nx release feature. But the nx-api release page still says its in APHA, can you please confirm if Nx release is production ready now?

[@nxdevtools]

we fixed that.

[@kincham487]

Is there anyone who can please help me? I followed the instructions in this video, but when I execute "nx release", everything seems to be fine in my console. However, it does not create releases in my Github repository. I have been stuck on this issue for days!

[@Yves-u4i]

Bump version

[@Yves-u4i]

You're making too much break changes from a release to another. Real app can't work with nx. Each time we have to learn "the new way" to do basic things. Also, why to do all in 1?? My personal case is to grt the dependencies, i have my owns scripts in my ci cd. You make it very hard