From 4c65da43745bb9205a6ff2dcaad8ba080f3369ff Mon Sep 17 00:00:00 2001 From: Daniel McCoy Stephenson Date: Tue, 17 Nov 2026 21:09:46 -0700 Subject: [PATCH 1/2] docs(releasing): note that publish.yml needs a three-part v tag The v*.*.* trigger needs two dots after the v, so a tag such as v1.0 never starts the workflow even when it equals v + __version__. The doc claimed every mismatched v-prefixed tag fails the build loudly. Co-Authored-By: Claude Opus 5.5 --- RELEASING.md | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/RELEASING.md b/RELEASING.md index 96a37c0..5d58266 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -47,10 +47,15 @@ this repository: - publishes to PyPI via Trusted Publishing. The tag must equal `v` + `__version__` (e.g. `__version__ = "0.2.0"` → tag -`v0.2.0`). A `v`-prefixed tag whose version does not match `__version__` fails -the build before anything is published. A tag **without** the `v` prefix fails -silently instead: it matches no trigger in `publish.yml`, so the workflow never -runs and nothing reports the missed release. The `0.2.0` and +`v0.2.0`), and `__version__` must have at least three dot-separated parts, +because the trigger in `publish.yml` is the glob `v*.*.*`, which needs two dots +after the `v`. A tag that matches the trigger but whose version does not match +`__version__` fails the build before anything is published. A tag that does +not match the trigger fails silently instead: the workflow never runs and +nothing reports the missed release. That covers a tag **without** the `v` +prefix, and also a `v`-prefixed tag with fewer than three parts such as +`v1.0` — even when it equals `v` + `__version__`. (The `v0.1` tag on this +repository is of that shape, and would not trigger the workflow either.) The `0.2.0` and `0.3.0.dev20260808` tags were pushed that way, so the publish workflow has never run (tracked in [#34](https://github.com/Stephenson-Software/graphik/issues/34)). From ee24d343dc2d7bbbac32c3b972220f1a1cbfd0a7 Mon Sep 17 00:00:00 2001 From: Daniel McCoy Stephenson Date: Tue, 17 Nov 2026 21:10:21 -0700 Subject: [PATCH 2/2] docs(releasing): disambiguate which tags lacked the v prefix Co-Authored-By: Claude Opus 5.5 --- RELEASING.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/RELEASING.md b/RELEASING.md index 5d58266..4f84414 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -55,9 +55,9 @@ not match the trigger fails silently instead: the workflow never runs and nothing reports the missed release. That covers a tag **without** the `v` prefix, and also a `v`-prefixed tag with fewer than three parts such as `v1.0` — even when it equals `v` + `__version__`. (The `v0.1` tag on this -repository is of that shape, and would not trigger the workflow either.) The `0.2.0` and -`0.3.0.dev20260808` tags were pushed that way, so the publish workflow has never -run (tracked in +repository is of that shape, and would not trigger the workflow either.) The +`0.2.0` and `0.3.0.dev20260808` tags were pushed without the prefix, so the +publish workflow has never run (tracked in [#34](https://github.com/Stephenson-Software/graphik/issues/34)). ## Installing (after the first publish)