Is there any stable version?

[daniyal-preesoft]

I have tried three different versions in the last two days 3.8.38, 3.8.39, and 3.8.40, and two of them i.e., 3.8.38 and 3.8.40, failed to start. I'm not sure if I should keep using 3.8.39 because the following versions mention a lot of bug fixes.

Is there any stable version with which at least most things work if not all?

Please note this is not a request to add a stable release channel because that has already been asked and being tracked internally as per: #1134

My question is only toward the community if they know a recent enough stable version for which most features work.

[diegosouzapw]

Hey @daniyal-preesoft! Short answer: run the latest published release, v3.8.42 (npm i -g omniroute@latest, or the :latest Docker tag). That is the current latest on npm and the most stable line right now. Since v3.8.39 already boots for you, upgrading to v3.8.42 should be smooth -- .42 rolled up a large batch of provider/routing fixes on top of .39.

Two things about the versions you tried:

• v3.8.41 had a real boot regression -- dist/tls-options.mjs was pruned from the published package, so it crashed on startup. Fixed in v3.8.42 (fix(cli): restore dist/tls-options.mjs to npm tarball (#5452) #5503), which is one reason to jump straight to .42.
• A "failed to start" on v3.8.38 / v3.8.40 specifically is not a pattern I have seen reported, so it may be environment-specific (Node version, data dir, a stale .env, or a half-installed global). v3.8.42 needs Node >=22 <23 or >=24 <27.

If v3.8.42 also fails to start, that is a bug I want to trace -- please open a new [bug] issue with the exact boot error / stack (run with APP_LOG_LEVEL=debug), your node -v, and OS.

(And yes -- a formal stable/LTS channel is the separate ask you linked; this is just the "which recent version works" community answer.)