Skip to content

Fix dev distance versioning on main #510

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
evertlammerts merged 1 commit into from
Jun 26, 2026
Merged

Fix dev distance versioning on main #510

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions pyproject.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,6 +88,12 @@ version_scheme = "duckdb_packaging.setuptools_scm_version:version_scheme"
local_scheme = "no-local-version"
fallback_version = "0.0.1.dev1"

# main only: count dev distance from the last *minor* tag (v*.*.0), so a patch
# tag (e.g. v1.5.4) merged in from a release branch can't reset .devN.
# Release branches must NOT have this, they correctly count from v*.*.* (the default).
[tool.setuptools_scm.scm.git]
describe_command = "git describe --dirty --tags --long --abbrev=40 --match v*.*.0"

# Override: if COVERAGE is set then:
# - we create a RelWithDebInfo build
# - we make sure we use a persistent build dir so we get access to the .gcda files
Expand Down
Loading