Mercurial > public > mercurial-scm > hg
changeset 52972:40c5e29f817a
version: update the generation to something closer to what we had previously
When we moved to use setuptools-scm in 30510238284e, we lost the version scheme
that was engineers to make it safe to produce and consume nightly build from
multiple branches (stable, default, and privates branches).
This small change give use something close to what we have, but still don't
support multiple branch.
| author | Pierre-Yves David <pierre-yves.david@octobus.net> |
|---|---|
| date | Wed, 19 Feb 2025 00:25:17 +0100 |
| parents | c636f2835c95 |
| children | ef4192dec3d3 |
| files | pyproject.toml |
| diffstat | 1 files changed, 10 insertions(+), 0 deletions(-) [+] |
line wrap: on
line diff
--- a/pyproject.toml Wed Feb 19 01:13:00 2025 +0100 +++ b/pyproject.toml Wed Feb 19 00:25:17 2025 +0100 @@ -118,3 +118,13 @@ [tool.setuptools_scm] version_file = "mercurial/__version__.py" + +# this use `<last-tag>.post1.dev<distance> +# +# To restore the format introduced for 6.9 nightly build we would need to be +# able to customise the `post1` section to avoid flip-flopping update between +# unrelated branches. It would need to be changed to: +# - post0: for the "stable" branch +# - post1: for the "default" branch +# - post2: for any other branch +version_scheme = "no-guess-dev"