Open noirbizarre opened 4 months ago
Not sure whether we need to create a 4.0
branch 🤔
I'm thinking of splitting version_schemes into smaller modules. Make both version_schemes and providers pluggable
I'm thinking of splitting version_schemes into smaller modules
good idea, to be in-line with providers, and it would be easier to find them
Make both version_schemes and providers pluggable
what do you mean? they are already plugins, right?
what do you mean? they are already plugins, right?
ah, you're right. I forget it 🤦♂️
We should improve the templates to make it easier to extend
Brainstorming a few ideas (doesn't mean that we need everything in the next major):
alt-tag-formats
: to handle tag format changes. Legacy tags can still be parsed and included in the changelogignore-tag-formats
: tag that are expected and should be ignored (should not result in a warning)pydantic
:
pre
and post
bump hooks (entrypoints):
Given there is an autobump, maybe we can formalize a process to group new features and breaking changes together to reduce the bump of major/minor releases. Maybe using merge queues. I did not yet research what exists for that.
Most of them look good.
I would avoid relying on pydantic
as it's a widely used library. A lot of people attach commitizen to their dev-dependencies, and a lot of ppl use pydantic 1 or 2, probably creating problem. I heard today someone having issues with charset-normalizer
I also think https://github.com/commitizen-tools/commitizen/issues/950 might be something we want to correctly handle but could potential be a breaking change due to the difference between python packaging versioning and semver
Should we change this into a discussion and maybe create a few issues related to it? This looks more like a discussion instead of an issue to me
We might also want to include this one https://github.com/commitizen-tools/commitizen/pull/1209
Description
Discuss and tracking breaking changes to include in the next major release.
Possible Solution
--version-type
Additional context
Should we release a major by breaking change or group them into a single major release ?
Additional context
No response