From b1aab14a79a3074a27455400da5acd2039b52ed5 Mon Sep 17 00:00:00 2001 From: Daniel McCoy Stephenson Date: Sat, 14 Nov 2026 20:04:19 -0700 Subject: [PATCH 1/2] docs: unprefixed release tags run nothing, not fail fast RELEASING.md said a tag not equal to v + __version__ fails the build fast. That only holds for a v-prefixed tag; an unprefixed one matches no publish.yml trigger and runs nothing, which is how 0.2.0 and 0.3.0.dev20260808 went unpublished (#34). README's Installation note also tied PyPI availability to a release being tagged, though tags exist and none was published. Co-Authored-By: Claude Opus 5.5 --- README.md | 2 +- RELEASING.md | 8 +++++++- 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index c807f2a..0e09ffd 100644 --- a/README.md +++ b/README.md @@ -6,7 +6,7 @@ This library assists developers with graphics programming. ## Installation `graphik` has not been published to PyPI yet (see [RELEASING.md](RELEASING.md) for the release process), so `pip install graphik` will not resolve until the -first release is tagged. Until then, install directly from this repository: +first release is published. Until then, install directly from this repository: ```bash pip install git+https://github.com/Stephenson-Software/graphik.git ``` diff --git a/RELEASING.md b/RELEASING.md index 3c0398e..a60fb00 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -47,7 +47,13 @@ this repository: - publishes to PyPI via Trusted Publishing. The tag must equal `v` + `__version__` (e.g. `__version__ = "0.2.0"` → tag -`v0.2.0`), or the build fails fast before anything is published. +`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 +`0.3.0.dev20260808` tags were pushed that way, which is why no release has been +published yet (tracked in +[#34](https://github.com/Stephenson-Software/graphik/issues/34)). ## Installing (after the first publish) From 7ace2f95d02e0c491d0b9aede3c3e59be0716144 Mon Sep 17 00:00:00 2001 From: Daniel McCoy Stephenson Date: Sat, 14 Nov 2026 20:05:26 -0700 Subject: [PATCH 2/2] docs: state only the verified consequence of the unprefixed tags The workflow never running is observable; whether PyPI's one-time setup would also have blocked a publish is not, so drop the causal claim. Co-Authored-By: Claude Opus 5.5 --- RELEASING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/RELEASING.md b/RELEASING.md index a60fb00..96a37c0 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -51,8 +51,8 @@ The tag must equal `v` + `__version__` (e.g. `__version__ = "0.2.0"` → tag 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 -`0.3.0.dev20260808` tags were pushed that way, which is why no release has been -published yet (tracked in +`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)). ## Installing (after the first publish)