commit f61b416c6f792d3ef1c2799263ff012db8613115
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Sep 28 09:46:32 2026 +0200

dev-python/pyvista-validation: drop 0.2.3

With 0.5.4 in, 0.2.3 falls outside the last three releases. 0.2.2
stays because pyvista pins ~0.2.2.

commit f6a351a713a5bb78a257196a861748127e64f7fe
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Sep 28 09:46:08 2026 +0200

dev-python/pyvista-validation: add 0.5.4

The release only narrows the return types in the @overload signatures
of validate_rotation, validate_transform3x3 and validate_transform4x4.
The build interface and dependencies are unchanged. pyvista pins
~0.2.2, so this release has no consumer in the tree yet.

commit aa2f3d4629f8de9bb6ddae7515f00adff45e6ae2
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sun Sep 27 09:37:41 2026 +0200

dev-python/pyvista-validation: add 0.5.3

Upstream raises its NumPy floor to 1.22, so RDEPEND follows. The C
extension still targets the 1.21 C API, and the comment now says
that rather than calling 1.21 the runtime floor. pyvista pins
~0.2.2, so this release has no consumer in the tree yet.

commit 7f11f3c1ef7b75b064c4c50107d6400e706f9c2a
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sat Sep 26 12:03:49 2026 +0200

dev-python/pyvista-validation: add 0.3.0

validate_transform4x4 now returns float64 for non-floating input
instead of keeping integer dtypes. Runtime and build dependencies are
unchanged; only upstream's dev and docs pins moved.

pyvista 0.49.0 pins ~0.2.2 and is unaffected.

commit 43c8a2f96c88e43c777876d6d033dcb9487d5104
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Fri Sep 25 09:31:52 2026 +0200

dev-python/pyvista-validation: Keyword 0.2.3 for ~arm

The C extension code has no architecture-specific handling in the
ebuild.

commit 020a493e3b85e43cbc49edaddb59f869eb53836f
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Fri Sep 11 10:46:10 2026 +0200

dev-python/pyvista-validation: trim 0.2.2 comments

commit 98dc7eb73d3c3adec486a4c4512dddccc08a314c
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Fri Sep 11 00:49:21 2026 +0200

dev-python/pyvista-validation: trim 0.2.3 comments

commit b1f0c369dea3b2d672e5ddcc2e703b492d725719
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Fri Sep 11 00:04:21 2026 +0200

dev-python/pyvista-validation: isolate 0.2.2 tests

Ambient plugins and source-tree imports can mask the installed package
behavior, so the suite needs an isolated pytest environment.

commit fe94b6f8e10aa2767e1c7836403abd6d5a846673
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Sep 10 17:49:46 2026 +0200

dev-python/pyvista-validation: add 0.2.3

Run the test suite outside the source package so it exercises the
built C extension.

commit 232b2bd440ffd6f803db391b09da1f03e580ecd0
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Tue Sep 8 09:01:51 2026 +0200

dev-python/pyvista-validation: new package, add 0.2.2

pyvista 0.49.0 splits its pyvista._validation subpackage out into this
standalone distribution and == pins it, importing it at module scope in 29
places, so it is a hard runtime dependency rather than an optional extra.
Nothing in ::gentoo or ::guru carries it.

numpy appears in both BDEPEND and RDEPEND at different floors on purpose:
setup.py compiles src/fast against the NumPy 2 headers, while
NPY_TARGET_VERSION keeps the result loadable against the 1.21 runtime floor
upstream declares. The extension is marked optional() upstream and the
package falls back to pure Python without it.

python_test overrides addopts because upstream pins --cov and
--cov-fail-under=95 there; epytest runs with the plugin disabled, so those
would arrive as unrecognised arguments and abort the run before collection.

PYTHON_COMPAT stops at 3.14 to match upstream's classifiers, so the
python3_15 suggestion from pkgcheck is not acted on.