head	1.4;
access;
symbols
	pkgsrc-2025Q4:1.2.0.6
	pkgsrc-2025Q4-base:1.2
	pkgsrc-2025Q3:1.2.0.4
	pkgsrc-2025Q3-base:1.2
	pkgsrc-2025Q2:1.2.0.2
	pkgsrc-2025Q2-base:1.2;
locks; strict;
comment	@# @;


1.4
date	2025.12.28.15.39.43;	author gdt;	state dead;
branches;
next	1.3;
commitid	g20wbnOfZqabQboG;

1.3
date	2025.12.26.10.49.13;	author adam;	state Exp;
branches;
next	1.2;
commitid	o9WUy6Q4eM5MjUnG;

1.2
date	2025.05.02.07.11.51;	author adam;	state Exp;
branches;
next	1.1;
commitid	EYPNpm0uxPbuLiTF;

1.1
date	2025.04.22.11.28.13;	author adam;	state Exp;
branches;
next	;
commitid	TlS4OfTQU6Rwv2SF;


desc
@@


1.4
log
@devel/py-pydantic-*: Drop incorrect relaxation of exact dep and add caution

As posted to tech-pkg on 5 December, pydantic really does have an
exact dependency on pydantic-core (even though the version numbers do
not match).  The previous update was broken, and matrix-synapse failed
to build.

Drop the patch to pyproject.toml that relaxes the dependency, as 1)
wrong and 2) not documented or reported upstream (who would say no,
it's right).

Add comments that these two packages need to be updated in sync with
version numbers that meet upstream's dependency patterns.

No PKGREVISION++, as the binary package doesn't change.  It's just
that a future bad update will cause a build failure, if someone does
that without reading the comments.
@
text
@$NetBSD: patch-pyproject.toml,v 1.3 2025/12/26 10:49:13 adam Exp $

Relax pydantic-core version requirement.

--- pyproject.toml.orig	2020-02-02 00:00:00.000000000 +0000
+++ pyproject.toml
@@@@ -48,7 +48,7 @@@@ dependencies = [
     'typing-extensions>=4.14.1',
     'annotated-types>=0.6.0',
     # Keep this in sync with the version in the `check_pydantic_core_version()` function:
-    'pydantic-core==2.41.5',
+    'pydantic-core>=2.41.5',
     'typing-inspection>=0.4.2',
 ]
 dynamic = ['version', 'readme']
@


1.3
log
@py-pydantic: updated to 2.12.5

2.12.5 (2025-11-26)

This is the fifth 2.12 patch release, addressing an issue with the `MISSING` sentinel and providing several documentation improvements.

The next 2.13 minor release will be published in a couple weeks, and will include a new *polymorphic serialization* feature addressing
the remaining unexpected changes to the *serialize as any* behavior.

* Fix pickle error when using `model_construct()` on a model with `MISSING` as a default value
* Several updates to the documentation
@
text
@d1 1
a1 1
$NetBSD: patch-pyproject.toml,v 1.2 2025/05/02 07:11:51 adam Exp $
@


1.2
log
@py-pydantic: updated to 2.11.4

v2.11.4 (2025-04-29)

Packaging

* Bump `mkdocs-llmstxt` to v0.2.0

Changes

* Allow config and bases to be specified together in `create_model()`
  This change was backported as it was previously possible (although not meant to be supported)
  to provide `model_config` as a field, which would make it possible to provide both configuration
  and bases.

Fixes

* Remove generics cache workaround
* Remove coercion of decimal constraints
* Fix crash when expanding root type in the mypy plugin
* Fix issue with recursive generic models
* Traverse `function-before` schemas during schema gathering
@
text
@d1 1
a1 1
$NetBSD: patch-pyproject.toml,v 1.1 2025/04/22 11:28:13 adam Exp $
d5 1
a5 1
--- pyproject.toml.orig	2025-04-22 11:23:12.931012242 +0000
d7 2
a8 2
@@@@ -46,7 +46,7 @@@@ dependencies = [
     'typing-extensions>=4.12.2',
d11 3
a13 3
-    'pydantic-core==2.33.2',
+    'pydantic-core>=2.33.2',
     'typing-inspection>=0.4.0',
@


1.1
log
@py-pydantic: relax pydantic-core version requirement; add TEST_DEPENDS
@
text
@d1 1
a1 1
$NetBSD$
d11 2
a12 2
-    'pydantic-core==2.33.1',
+    'pydantic-core>=2.33.1',
@