v0.4.2

Supersedes v0.4.1, which published to TestPyPI and then failed its verify step on a quoting bug in this repository's own release workflow, so it never reached PyPI. The content below is identical.

Fixed

• memray and pyre-check no longer break a Windows install. Both were declared for every platform and neither exists on Windows: each publishes MacOS and POSIX::Linux classifiers with no Windows wheel, and pyre-check pulls testslide, which is Linux-only. uv sync therefore tried to build all three from source on Windows, and memray's scikit-build-core/CMake configure fails against Visual Studio 17:

  × Failed to build `memray==1.20.0`
  ╰─▶ Call to `scikit_build_core.build.build_wheel` failed (exit code: 1)
      -- Building for: Visual Studio 17 2022
      *** CMake configuration failed
  

  That broke the whole resolution rather than skipping a profiler, so provide-testkit[profiling] and provide-testkit[typecheck] could not be installed on Windows at all — nor could anything depending on them. Both are now marked sys_platform != 'win32'. viztracer, mypy, pyright, pyrefly and ty are unaffected and still install everywhere.

• The TestPyPI verify step could never pass. Its import snippet nested double quotes inside a double-quoted shell argument, so Python received v = version(provide-testkit) — a subtraction — and raised NameError: name 'testkit' is not defined after a completely successful install.

Build

• Dropped the [tool.uv.sources] path dependency on provide-foundation. CI and the release build check out a single repository, so uv sync had no sibling checkout to resolve it against. Local development installs siblings with uv pip install -e.