astral-sh/uv · error
{old_version} => {new_version} didn't increase the version;
Error message
{old_version} => {new_version} didn't increase the version; provide the exact version to force an update What it means
Error "{old_version} => {new_version} didn't increase the version; provide the exact version to force an update" thrown in astral-sh/uv.
Source
Thrown at crates/uv/src/commands/project/version.rs:320
value: spec.value,
}),
VersionBump::Post => new_version.bump(BumpCommand::BumpPost { value: spec.value }),
VersionBump::Dev => new_version.bump(BumpCommand::BumpDev { value: spec.value }),
}
}
if new_version <= old_version {
if old_version.is_stable() && new_version.is_pre() {
return Err(anyhow!(
"{old_version} => {new_version} didn't increase the version; when bumping to a pre-release version you also need to increase a release version component, e.g., with `--bump <major|minor|patch>`"
));
}
if new_version.is_dev() && !old_version.is_dev() {
return Err(anyhow!(
"{old_version} => {new_version} didn't increase the version; when bumping to a dev version you also need to increase another version component, e.g., with `--bump <major|minor|patch|alpha|beta|rc>`"
));
}
return Err(anyhow!(
"{old_version} => {new_version} didn't increase the version; provide the exact version to force an update"
));
}
Some(new_version)
} else {
None
};
// Update the toml and lock
let status = if dry_run {
ExitStatus::Success
} else if let Some(new_version) = &new_version {
let project = update_project(
project,
new_version,
&mut toml,
&pyproject_path,View on GitHub (pinned to f1a42680ff)
When it happens
Trigger: Thrown at crates/uv/src/commands/project/version.rs:320 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of astral-sh/uv@f1a42680ff (2026-08-16).
Data as JSON: /api/errors/dd07d2cfdcc494aa.
Report an issue: GitHub.