At the moment, our release pipeline for https://github.com/aligent/microservice-development-utilities only support 1 version for all packages. Our release process is:

Manually create new release in Github.

Once a release is created, Github add a git tag.

Our release pipeline will use that git tag to release the new version.

This process works fine in a poly repository where we only release 1 package at a time. However, it doesn’t work as intended in our new mono repository where we have multiple packages with different versions.

I suggest that we move to a different release process where we release when something is merged into main branch. This process has some benefit:

We automate the whole release process. No more manual step.

We can easily control package versions individually. Nx will read the version number from package.json file and check if the same package exists or not on npm to decide if it should publish it or not.

During PR and merge process, we have to ensure we produce something publishable.

I think there are couple of way to solve this and this is just my suggestion and open for discussion.