* 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>

Signed-off-by: Edgar Ramírez Mondragón <edgarrm358@gmail.com>

Provide an external Rust backend (fast-semver-rs-backend)

* Pure-Python parser remains default; opt-in only
* Document optional [native] extra in install.rst
* Backend fast-semver-rs-backend accelerates parsing on CPython
* Add towncrier newsfragment pr476.feature.rst


---------

Co-authored-by: lowmiaq-gmail <lowmiaq-gmail@users.noreply.github.com>
Co-authored-by: Cursor Agent <cursoragent@cursor.com>

Co-authored-by: Codex <noreply@openai.com>

…s build metadata (#480)

`semver.version.Version.bump_build` will now add `.0` to an existing
build when the last segment of the current build metadata, split by dots
(`.`), is not numeric.

This is to ensure the bumped version contains a raised build instead
of silently returning an unchanged version.

For example, `1.2.3+alpha` is bumped to `1.2.3+alpha.0`. This mirrors the
corresponding fix for the prerelease part (#460).

Related to #466.

Ignoring the optional Rust backend fallback.

Comparing a `Version` with a `dict`, `tuple`, or `list` that cannot construct a
valid version (for example, an empty collection, wrong number of parts,
non-numeric parts, or unknown keys) no longer raises internal errors
from `Version.__init__`.

The comparison operators now return `NotImplemented` for such operands,
following the general rule for invalid comparison operand types: equality
evaluates to `False` and ordering raises Python's standard `TypeError`
(for example, `>` not supported between instances of 'Version' and 'dict'`).

* Update GitHub Action steps
* Update list of contributors. Thanks to all!