Feedback: smaller, more frequent stable releases

[70nyIT]

Hi, and thanks for the work on OmniRoute. I use it daily and it is central to my setup.

My feedback is about release cadence. v3.8.51 shipped on Sep 30, and 3.8.52 is still in progress almost three weeks later. Several fixes I depend on are merged but not available on a stable release:

• Ollama Cloud model discovery (fix(providers): Ollama Cloud — no models available since yesterday #16823, fixed in Fix/16823 ollama cloud live model discovery #16856). deepseek-v4.1-flash is not in the catalog because the old parser falls back to the static list.
• The configurable tool-list cap (feat(backend): Make tool-list cap (MAX_TOOLS_LIMIT=128) configurable via env var #13190), closed on Oct 8. I reported it on Sep 10.

I know :next exists, but I would rather stay on stable. Would you consider cutting smaller patch releases more often, even weekly, for provider and catalog fixes? Providers add models quickly, so these fixes go stale fast. The bigger features could keep their own cycle.

Thanks for considering it. This is meant as a suggestion, not a complaint.

[maxmad64bis]

I'm not sure if this is a release issue or an architectural limitation. There is a lot of hardcoded configuration in the release for both the provider and the catalog. It has been a nightmare of endless patches and rebuilds just to keep up with provider changes.

@diegosouzapw, any thoughts on this? Is this design choice intentional, or is it just a de facto situation? I think there are many alternatives worth investigating to make us more agile. (Keeping in mind that this might mean a major upgrade with some risks).

[maxmad64bis]

A quick-win: #17285

[diegosouzapw]

@70nyIT Thanks for the concrete feedback. A factual update first: v3.8.52 was published on 2026-10-19, and I checked the release tag for the two fixes you named: the Ollama Cloud discovery change (#16823, the /api/tags path is in the provider discovery code) and the configurable tool-list cap (OMNIROUTE_MAX_TOOLS_LIMIT, default 128). Both are in 3.8.52 now.

Release cadence and how much of the provider/catalog data is hardcoded are decisions for the maintainer, so I can't answer them, and I'm leaving @maxmad64bis's architecture question for @diegosouzapw as well. I'll flag this thread so it gets an answer.