Repository navigation
Separate version providers from core #1676
Description
Activity
Splitting
commitizen/providers/*.pyinto separate optional packages would be a substantial refactor (changes topyproject.tomlpackaging,entry-pointsregistration, CI / publishing pipeline, plus a deprecation cycle for users who currently import providers directly fromcommitizen.providers).This is the kind of structural change that wants to land on a major boundary alongside the rest of v5. Surfaced via the round-2 triage in #1965 — proposing this be re-scoped under #1481 (v5 release tracker) and not picked up as a 4.x improvement.
Description
Not all of the version providers are needed by commitizen core all the time. We could probably try something like an Airflow provider and use uv workspace to help us manage it.
Possible Solution
No response
Additional context
No response
Related issues
No response