pinecrew / pined-django / 33437102197

95%

push

github

repo: take the version from the tag, not from pyproject

`version` is `dynamic`, and `hatch-vcs` reads it out of git when the package is
built. Nothing in the repository states a version any more, so nothing can
disagree with the tag about what is being released.

That means leaving `uv_build`, which has no dynamic version to offer — it
refuses to build a project without a literal `version` field. Two blocks of
hatchling configuration keep the distributions as they were: `packages` for the
`pined.django` namespace layout, and `only-include` for the sdist, since
hatchling otherwise ships the whole repository where `uv_build` shipped the
package and its paperwork.

`release.yml` loses its version step — `uv version` cannot set a dynamic one —
and gains two guards. `hatch-vcs` does not fail when it cannot find a tag; it
produces `0.1.dev38+g9c4a7ad` and carries on, which locally is exactly right
and in a release is a silent mispublish. So the job checks out with
`fetch-depth: 0`, a shallow clone having no tags to read, and refuses to upload
a version carrying `dev` or a `+local` part.

`uv.lock` records the project as `(dynamic)` rather than pinning a version, so
the version moving with every commit costs no lock churn.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

201 of 246 branches covered (81.71%)

Branch coverage included in aggregate %.

1113 of 1302 relevant lines covered (85.48%)

0.85 hits per line