Skip to content

Commit 7f9edcc

Browse files
committed
Document tagging conventions
Backport of: #13128
1 parent b46a0c9 commit 7f9edcc

1 file changed

Lines changed: 10 additions & 1 deletion

File tree

‎docs/version-policy.md‎

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,16 @@ In all cases we will aim to minimize churn and do so only when justified by the
3434

3535
## Pydantic V3 and beyond
3636

37-
We expect to make new major releases roughly once a year going forward, although as mentioned above, any associated breaking changes should be trivial to fix compared to the V1-to-V2 transition.
37+
Any associated breaking changes in the V3 release will be introduced with care. This will include bug fixes that can't be solved in V2 without introducing a change in behavior
38+
(e.g. [fixing configuration not following the MRO](https://github.com/pydantic/pydantic/issues/9992)), or changes that don't remove existing functionality or doesn't provide
39+
proper alternatives.
40+
41+
In V3, it is expected to merged `pydantic-core` as an internal sub-module of Pydantic, meaning it won't be published as a standalone library anymore.
42+
43+
## Tagging conventions
44+
45+
Pydantic uses Git tags to identify all published versions on PyPI (including alpha and beta releases), prefixed with the `v` character. Since v2.13, `pydantic-core`
46+
has been merged as a workspace member inside the `pydantic` repository, and subsequent `pydantic-core` releases are tagged as `core-vx.y.z`.
3847

3948
## Experimental Features
4049

0 commit comments

Comments
 (0)