Update dependency semver to v3.1.0

renovate commented

2026-09-12 23:33:05 +02:00

Collaborator

This PR contains the following updates:

Package	Change	Age	Confidence
semver (changelog)	`==3.0.4` → `==3.1.0`

⚠️ Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

python-semver/python-semver (semver)

`v3.1.0`

Compare Source

=============

:Released: 2026-09-12
:Maintainer: Tom Schraitle

Bug Fixes

:pr:478: Version.parse() and Version.is_valid() now reject non-ASCII digits and
trailing newlines, in accordance with the SemVer grammar. Optional minor and
patch parsing applies the same character restrictions.
:pr:479: Comparing a :class:~semver.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 :py:const:NotImplemented for such operands, following the general rule for invalid comparison operand types: equality evaluates to False and ordering raises Python's standard :py:exc:TypeError (for example, '>' not supported between instances of 'Version' and 'dict').
:pr:480: (:meth:~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 (:gh:460). Related to :gh:466.
:gh:460: :meth:~semver.version.Version.bump_prerelease will now add .0 to an
existing prerelease when the last segment of the current prerelease, split by
dots (.), is not numeric. This is to ensure the new prerelease is considered
higher than the previous one.

:meth:~semver.version.Version.bump_prerelease now also support an argument
bump_when_empty which will bump the patch version if there is no existing
prerelease, to ensure the resulting version is considered a higher version than
the previous one.

Features

:pr:476: Added optional [native] extra to accelerate parsing on CPython via the
fast-semver-rs-backend package. The pure-Python parser remains the default;
the native backend is opt-in and only available on CPython.

Internal Changes

: Update GitHub Actions for astral-sh/setup-uv (version 0.10.1), github/codeql-action (version 4)

Trivial Changes

:gh:463: Remove double code in :meth:Version.bump_build

: Improve test coverage to 100% by ignoring the optional Rust backend fallback.: Improve test suite for comparisons and fix test coverage.; Suppress deprecation warnings in test suite.

Configuration

📅 Schedule: (UTC)

Branch creation
- At any time (no schedule defined)
Automerge
- At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [semver](https://github.com/python-semver/python-semver) ([changelog](https://python-semver.readthedocs.io/en/latest/changelog.html)) | `==3.0.4` → `==3.1.0` | ![age](https://developer.mend.io/api/mc/badges/age/pypi/semver/3.1.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/semver/3.0.4/3.1.0?slim=true) | --- > ⚠️ **Warning** > > Some dependencies could not be looked up. Check the [Dependency Dashboard](issues/8) for more information. --- ### Release Notes <details> <summary>python-semver/python-semver (semver)</summary> ### [`v3.1.0`](https://github.com/python-semver/python-semver/blob/HEAD/CHANGELOG.rst#Version-310) [Compare Source](https://github.com/python-semver/python-semver/compare/3.0.4...3.1.0) \============= :Released: 2026-09-12 :Maintainer: Tom Schraitle ## Bug Fixes - :pr:`478`: `Version.parse()` and `Version.is_valid()` now reject non-ASCII digits and trailing newlines, in accordance with the SemVer grammar. Optional minor and patch parsing applies the same character restrictions. - :pr:`479`: Comparing a :class:`~semver.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 :py:const:`NotImplemented` for such operands, following the general rule for invalid comparison operand types: equality evaluates to `False` and ordering raises Python's standard :py:exc:`TypeError` (for example, `'>' not supported between instances of 'Version' and 'dict'`). - :pr:`480`: (:meth:`~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 (:gh:`460`). Related to :gh:`466`. - :gh:`460`: :meth:`~semver.version.Version.bump_prerelease` will now add `.0` to an existing prerelease when the last segment of the current prerelease, split by dots (`.`), is not numeric. This is to ensure the new prerelease is considered higher than the previous one. :meth:`~semver.version.Version.bump_prerelease` now also support an argument `bump_when_empty` which will bump the patch version if there is no existing prerelease, to ensure the resulting version is considered a higher version than the previous one. ## Features - :pr:`476`: Added optional `[native]` extra to accelerate parsing on CPython via the `fast-semver-rs-backend` package. The pure-Python parser remains the default; the native backend is opt-in and only available on CPython. ## Internal Changes : Update GitHub Actions for astral-sh/setup-uv (version 0.10.1), github/codeql-action (version 4) ## Trivial Changes - :gh:`463`: Remove double code in :meth:`Version.bump_build` : Improve test coverage to 100% by ignoring the optional Rust backend fallback. : Improve test suite for comparisons and fix test coverage. : Suppress deprecation warnings in test suite. </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate).

renovate added 1 commit

2026-09-12 23:33:05 +02:00

Update dependency semver to v3.1.0

renovate/artifacts Artifact file update failure

e3633ae639

renovate commented

2026-09-12 23:33:05 +02:00

Author

Collaborator

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: requirements.txt

Post-upgrade command 'python -m fragcha renovate --data-file $RENOVATE_POST_UPGRADE_COMMAND_DATA_FILE' has not been added to the allowed list in allowedCommands

### ⚠️ Artifact update problem Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens: - any of the package files in this branch needs updating, or - the branch becomes conflicted, or - you click the rebase/retry checkbox if found above, or - you rename this PR's title to start with "rebase!" to trigger it manually The artifact failure details are included below: ##### File name: requirements.txt ``` Post-upgrade command 'python -m fragcha renovate --data-file $RENOVATE_POST_UPGRADE_COMMAND_DATA_FILE' has not been added to the allowed list in allowedCommands ```

renovate/artifacts Artifact file update failure

This pull request can be merged automatically.

You are not authorized to merge this pull request.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin renovate/semver-3.x:renovate/semver-3.x

git switch renovate/semver-3.x

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main

git merge --no-ff renovate/semver-3.x

git switch renovate/semver-3.x

git rebase main

git switch main

git merge --ff-only renovate/semver-3.x

git switch renovate/semver-3.x

git rebase main

git switch main

git merge --no-ff renovate/semver-3.x

git switch main

git merge --squash renovate/semver-3.x

git switch main

git merge --ff-only renovate/semver-3.x

git switch main

git merge renovate/semver-3.x

git push origin main

Rows
Columns

Update dependency semver to v3.1.0 #14

Release Notes

v3.1.0

Bug Fixes

Features

Internal Changes

Trivial Changes

Configuration

⚠️ Artifact update problem

File name: requirements.txt

Checkout

Merge

`v3.1.0`