Log message:
py-referencing: updated to 0.35.0

v0.35.0

* Ensure that ``Registry.contents()`` also raises ``NoSuchResource`` exceptions \ 
for nonexistent resources, not ``KeyError`` (which is an implementation detail).

Log message:
py-referencing: updated to 0.34.0

v0.34.0

* Also look inside ``definitions`` keywords even on newer dialects.
  The specification recommends doing so regardless of the rename to ``$defs``.

Log message:
py-referencing: updated to 0.33.0

v0.33.0
* Add a ``referencing.jsonschema.SchemaResource`` type alias to go along with \ 
the other JSON Schema specialized types.

Log message:
py-referencing: updated to 0.32.1

v0.32.1

* Make ``Specification.detect`` raise a ``CannotDetermineSpecification`` error \ 
even if passed a mapping with a ``$schema`` key that doesn't match JSON Schema \ 
dialect semantics (e.g. a non-string).

Log message:
py-referencing: updated to 0.32.0

v0.32.0

* Add ``Specification.detect``, which essentially operates like \ 
``Resource.from_contents`` without constructing a resource (i.e. it simply \ 
returns the detected specification).

Log message:
py-referencing: updated to 0.31.1

v0.31.1
* No user facing changes.

Log message:
py-referencing: updated to 0.31.0

v0.31.0

* Add ``referencing.jsonschema.EMPTY_REGISTRY`` (which simply has a convenient \ 
type annotation, but otherwise is just ``Registry()``).

Log message:
python/wheel.mk: simplify a lot, and switch to 'installer' for installation

This follows the recommended bootstrap method (flit_core, build, installer).

However, installer installs different files than pip, so update PLISTs
for all packages using wheel.mk and bump their PKGREVISIONs.

Log message:
py-referencing: updated to 0.30.2

v0.30.2
* Minor docs improvement.

Log message:
py-referencing: added version 0.30.1

An implementation-agnostic implementation of JSON reference
resolution.

In other words, a way for e.g. JSON Schema tooling to resolve the
$ref keyword across all drafts without needing to implement
support themselves.