updates:
- [github.com/astral-sh/ruff-pre-commit: v0.12.3 → v0.12.4](astral-sh/ruff-pre-commit@v0.12.3...v0.12.4)

…config

[pre-commit.ci] pre-commit autoupdate

updates:
- [github.com/astral-sh/ruff-pre-commit: v0.12.4 → v0.12.5](astral-sh/ruff-pre-commit@v0.12.4...v0.12.5)

…config

[pre-commit.ci] pre-commit autoupdate

Bumps [astral-sh/setup-uv](https://github.com/astral-sh/setup-uv) from 6.3.1 to 6.4.3.
- [Release notes](https://github.com/astral-sh/setup-uv/releases)
- [Commits](astral-sh/setup-uv@bd01e18...e92bafb)

---
updated-dependencies:
- dependency-name: astral-sh/setup-uv
  dependency-version: 6.4.3
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>

…ions/astral-sh/setup-uv-6.4.3

Bump astral-sh/setup-uv from 6.3.1 to 6.4.3

updates:
- [github.com/astral-sh/ruff-pre-commit: v0.12.5 → v0.12.7](astral-sh/ruff-pre-commit@v0.12.5...v0.12.7)

…config

[pre-commit.ci] pre-commit autoupdate

updates:
- [github.com/pre-commit/pre-commit-hooks: v5.0.0 → v6.0.0](pre-commit/pre-commit-hooks@v5.0.0...v6.0.0)
- [github.com/astral-sh/ruff-pre-commit: v0.12.7 → v0.12.8](astral-sh/ruff-pre-commit@v0.12.7...v0.12.8)

…config

[pre-commit.ci] pre-commit autoupdate

The runtime init signature of a validator can be seen with `inspect`:

```pycon
>>> import inspect, jsonschema
>>> inspect.signature(jsonschema.validators.Draft7Validator.__init__)
<Signature (self, schema: 'referencing.jsonschema.Schema', resolver=None, format_checker: '_format.FormatChecker | None' = None, *, registry: 'referencing.jsonschema.SchemaRegistry' = <Registry (20 resources)>, _resolver=None) -> None>
```

This aligns the protocol's declared signature with that behavior more
exactly with the following changes:

`registry` is now keyword-only, not keyword-or-positional, and has a
default.

`resolver` is added to the declared signature, so users who are using
it won't see typing-time discrepancies with the runtime. It is marked
as `Any` and commented inline as deprecated, since it's unclear what
else we could do to indicate its status.
This means that code passing a resolver will continue to type check
(previously it would not).

`resolver` is the second keyword-or-positional and `format_checker` is
the third, meaning that a positional-only caller who passes, for
example: `Draft202012Validator(foo, None, bar)` will have `foo`
slotted as the schema and `bar` as the `format_checker`
This would primarily impact callers with positional-args calling
conventions, but is more reflective of what they'll see at runtime.

In order to remove `resolver` from the protocol signature, but match
the runtime signatures well, some kind of placeholder is needed to
indicate `format_checker` as positional-or-keyword. Or else, a large
number of overloads for `__init__` could be declared to try to
simulate its removal.

Bumps [astral-sh/setup-uv](https://github.com/astral-sh/setup-uv) from 6.4.3 to 6.5.0.
- [Release notes](https://github.com/astral-sh/setup-uv/releases)
- [Commits](astral-sh/setup-uv@e92bafb...d9e0f98)

---
updated-dependencies:
- dependency-name: astral-sh/setup-uv
  dependency-version: 6.5.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>

Bumps [actions/checkout](https://github.com/actions/checkout) from 4 to 5.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](actions/checkout@v4...v5)

---
updated-dependencies:
- dependency-name: actions/checkout
  dependency-version: '5'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>

The typing tests are a new subdirectory of `jsonschema/tests/` which
are checked under a more stringent mypy configuration
(`--warn-unused-ignores`) in order to allow certain kinds of negative
tests against the declared types. [^1]

The first new test confirms that each validator matches the Validator
protocol, and furthermore that this is not vacuously true by way of
`Any`.

The test failed at first, as the return type of `create()` was not
annotated, and therefore under the declared types in `jsonschema`, all
of the validators were of type `Any`. To resolve, the return type of
`create` is now annotated as `type[Validator]`.

[^1]: Technically, the new nox configuration checks these files twice,
but only the second check, with `--warn-unused-ignores`, is doing all
of the necessary work.

for more information, see https://pre-commit.ci

Fix `Validator` protocol init to match runtime

…ions/actions/checkout-5

Bump actions/checkout from 4 to 5

…ions/astral-sh/setup-uv-6.5.0

Bump astral-sh/setup-uv from 6.4.3 to 6.5.0