FlexMeasures / flexmeasures / 34368219394

85%

push

github

Fix/guess next version (#2508)

* Refresh the flexmeasures package before regenerating OpenAPI specs

hatch-vcs computes the dynamic version from the closest reachable tag, but an
editable install only captures that computation once, at `uv sync` time - it
does not recompute on every `uv run`. A contributor whose venv was created (or
last synced) before a new tag landed therefore commits a stale
`openapi-specs.json` version field whenever the hook fires, without any error:
that is what happened after v1.1.0rc1 was tagged, where the file kept reading
"1.0.1" (guessed from v1.0.0) for several more commits instead of "1.1.0rc2".

Reinstalling just the flexmeasures package (not its dependencies) before
generating the spec is cheap (~1.5s) and forces hatch-vcs to recompute the
version from the current git state. The hook still no-ops in GitHub Actions.

Signed-off-by: F.N. Claessen <claessen@seita.nl>

* Parse the OpenAPI spec's version instead of splitting on dots

```.```.join(fm_version.split(".")[:3])``` mistook a pre-release suffix glued
onto the patch number for part of the version itself: for `1.1.0rc2.dev11+...`
it kept "1.1.0rc2" instead of "1.1.0", because PEP 440 attaches a pre-release
letter directly to the patch number (no dot), unlike the `.devN` segment. Use
`packaging.version.Version` to pull out major/minor/micro properly instead.

`packaging` was previously only a transitive dependency (via apispec, already
a hard dependency here) - declare it directly, since the code now imports it.

Signed-off-by: F.N. Claessen <claessen@seita.nl>

---------

Signed-off-by: F.N. Claessen <claessen@seita.nl>

1 of 3 new or added lines in 1 file covered. (33.33%)

18799 of 22064 relevant lines covered (85.2%)

0.85 hits per line