Log message:
py-validate-pyproject: updated to 0.15

Version 0.15
- Update ``setuptools`` schema definitions
- Add ``__repr__`` to plugin wrapper,
- Fix standard ``$schema`` ending ``#``

Log message:
py-validate-pyproject: updated to 0.14

Version 0.14
- Ensure reporting show more detailed error messages for \ 
``RedefiningStaticFieldAsDynamic``
- Add support for ``repo-review``

Log message:
py-validate-pyproject: updated to 0.13

Version 0.13
============
- Make it clear when using input from ``stdin``
- Fix summary for ``allOf``
- ``setuptools`` plugin:
    - Improve validation of ``attr`` directives

Log message:
py-validate-pyproject: updated to 0.12.2

Version 0.12.2
- ``setuptools`` plugin:
    - Fix problem with ``license-files`` patterns,
      by removing ``default`` value.

Version 0.12.1
- ``setuptools`` plugin:
    - Allow PEP 561 stub names in ``tool.setuptools.package-dir``,

Version 0.12
- ``setuptools`` plugin:
    - Allow PEP 561 stub names in ``tool.setuptools.packages``,

Version 0.11
- Improve error message for invalid replacements in the ``pre_compile`` CLI,
- Allow package to be build from git archive,
- Improve error message for invalid replacements in the ``pre_compile`` CLI,
- Error-out when extra keys are added to ``project.authors/maintainers``,
- De-vendor ``fastjsonschema``,

Version 0.10.1
- Ensure ``LICENSE.txt`` is added to wheel.

Version 0.10
- Add ``NOTICE.txt`` to ``license_files``,
- Use default SSL context when downloading classifiers from PyPI,
- Remove ``setup.py``,
- Explicitly limit oldest supported Python version
- Replace usage of ``cgi.parse_header`` with ``email.message.Message``

Log message:
*: use PYTHON_VERSION instead of _PYTHON_VERSION

Log message:
py-validate-pyproject: updated to 0.9

Version 0.9
- Use ``tomllib`` from the standard library in Python 3.11+

Version 0.8.1
- Workaround typecheck inconsistencies between different Python versions
- Publish :pep:`561` type hints

Version 0.8
- New :pypi:`pre-commit` hook
- Allow multiple TOML files to be validated at once via **CLI**
  (*no changes regarding the Python API*).

Log message:
py-validate-pyproject: updated to 0.7.2

Version 0.7.2
- ``setuptools`` plugin:
    - Allow ``dependencies``/``optional-dependencies`` to use file directives

Log message:
py-validate-pyproject: add missing build dependency on py-setuptools_scm

Log message:
py-validate-pyproject: added version 0.7.1

With the approval of PEP 517 and PEP 518, the Python community shifted towards
a strong focus on standardisation for packaging software, which allows more
freedom when choosing tools during development and make sure packages created
using different technologies can interoperate without the need for custom
installation procedures.

This shift became even more clear when PEP 621 was also approved, as a
standardised way of specifying project metadata and dependencies.

validate-pyproject was born in this context, with the mission of validating
pyproject.toml files, and make sure they are compliant with the standards and
PEPs. Behind the scenes, validate-pyproject relies on JSON Schema files, which,
in turn, are also a standardised way of checking if a given data structure
complies with a certain specification.