Turn our Markdown issue templates into YAML

Fix comparison with subclasses

* Allow uvx to be executed by tox
* Adjust building semver section
* Rework release procedure with uv
* Add restview to `pyproject.toml`
* Mention PEP 639 in `pyproject.toml`
* Update Changelog
* Extend `.readthedocs.yaml` with jobs

Release/3.0.3

* Raise version 3.0.3 -> 3.0.4
* Fix #457: Re-enable Trove license identifier
* Fix #456: Fix source dist file
  - Sort MANIFEST.in and add missing files
  - Add CONTRIBUTORS, .pytest.ini, .ruff.toml, and uv.lock
* Update Changelog

Fix 3.0.3

* Fix #463: Remove duplicate code Version.bump_build
* Update changelog

Raising a prerelease version always results in a newer version, and raising
an empty prerelease version has the option to raise the patch version as well

Co-authored-by: Tom Schraitle <tomschr@users.noreply.github.com>

---------

Co-authored-by: Bas Roos <bas.roos@enreach.com>
Co-authored-by: Tom Schraitle <tomschr@users.noreply.github.com>

* Update docs/advanced/combine-pydantic-and-semver.rst
* Update example with pydantic 2.10.5 semantic_version type

---------

Co-authored-by: Tom Schraitle <tomschr@users.noreply.github.com>

According to the Status of Python versions (https://devguide.python.org/versions/),
Python 3.7, 3.8, and 3.9 are already "end-of-life".

* Python 3.7: PEP 537, end of life 2023-06-27
* Python 3.8: PEP 569, end of life 2024-10-07
* Python 3.9: PEP 596, end of life 2025-10-31

=> For semver, the lowest supported Python version is Python 3.10 now.

Additional changes:

* Remove docformatter
* Add version identifiers for packages in `pyproject.toml`
* Update uv.lock

… docstrings (#471)

The docstrings in bump_major, bump_minor, bump_patch, bump_prerelease, bump_build, and next_version used semver.parse() which returns a plain dict, not a Version object. Calling instance methods like .bump_major() on a dict raises AttributeError.

Replace all 6 occurrences with semver.Version.parse() which correctly returns a Version instance, making the doctests runnable and accurate.

next_version('patch') on a version with build metadata but no prerelease
(e.g. 1.2.3+build.5) would strip the build and return the same version
(1.2.3) instead of bumping the patch (1.2.4).

The condition in next_version was (version.prerelease or version.build),
which caused build-only versions to enter the 'finalization' path meant
for prereleases. Build metadata does not affect version precedence, so
its presence should not trigger version finalization.

Change the condition to only check version.prerelease.

* docs: update next_version build-only example for new bump behavior

When next_version("prerelease", prerelease_token="rc") is called on a
version that already has a prerelease with a different token (e.g. dev),
bump_prerelease() ignores the token argument and simply increments the
existing counter. 1.2.4-dev.1 becomes 1.2.4-dev.2 instead of 1.2.4-rc.1.

Fix: before delegating to bump_prerelease, check whether the existing
prerelease token matches the requested one. When they differ, replace
the prerelease directly with "{prerelease_token}.1".

Bumps [cryptography](https://github.com/pyca/cryptography) from 49.0.0 to 50.0.0.
- [Changelog](https://github.com/pyca/cryptography/blob/main/CHANGELOG.rst)
- [Commits](pyca/cryptography@49.0.0...50.0.0)

---
updated-dependencies:
- dependency-name: cryptography
  dependency-version: 50.0.0
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>