ultra-runner VS semver

Cache built files to avoid rebuilds. For example nx.js, yarn-plugin-change, ultra-runner

Then comes the question of triggering docker builds if you need to release images. If you have many apps, it's better to create a docker file for each, so you can decide which one needs to be built. Nx help in this area, because it can compute which apps needs to be rebuilt... If you have only few apps you can use github action paths (ie: simplified example) or eventually make use of things like [ultra-runner](https://github.com/folke/ultra-runner). Anyway docker and nextjs take times to setup (env...). It's another story.

ultra-runner: scripts for JavaScripts monorepo management. Plugs in with Yarn, pnpm, and Lerna. Supports parallel building.

🏃 ultra-runner

Note, it is worth mentioning that the Nx community has also stepped up in the past and created jscutlery/semver, a package that adds semantic versioning and publishing to your Nx workspace. Make sure to check that out as well

In NX, I liked this one https://github.com/jscutlery/semver, but in TurboRepo, I didn't find anything like that, so I made my own.

@jscutlery/semver project is implementing this improvement

I don't quite follow the question, but it sounds like you may find Nx Semver useful? Nx is built on the premise that a repo represents a platform with a shared version, but the Semver plugin allows more flexibility for a project in the repo to run in "independent mode."