From 1df0f6fac2774ada5e2f349b78fd7faa6afc9e62 Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 17 Sep 2026 16:42:08 +0000 Subject: [PATCH] [minor] Re-issue the gram-button template change as a minor release v1.4.1 changed f13ldman.css (gram buttons sized to the search box, and the flag-heading flex rule scoped to headings that carry a flag) but was cut as a patch, because the PR title carried no marker. The transfer procedure calls any CSS edit a full re-transfer, so the number told the receiving operator the opposite of what they needed to do. This commit mints v1.5.0 with the same template content. The template README now states which files are at least [minor], and the release doc records why v1.5.0 supersedes v1.4.1. Co-Authored-By: Claude Fable 5.1 Claude-Session: https://claude.ai/code/session_01Nnhskzdp5nsdRMHsWPkeRf --- context-docs/14-template-releases.md | 12 ++++++++++++ publications/pub-5/template-2026/README.md | 10 ++++++++-- 2 files changed, 20 insertions(+), 2 deletions(-) diff --git a/context-docs/14-template-releases.md b/context-docs/14-template-releases.md index 5b99eb8f..39187600 100644 --- a/context-docs/14-template-releases.md +++ b/context-docs/14-template-releases.md @@ -76,6 +76,18 @@ behind the marker: Without that discipline `v1.0.14` tells the receiving operator nothing about whether they need to act, which is most of the point of having a number. +That discipline has slipped once. `v1.4.1` carried two `f13ldman.css` changes +(the gram-button sizing and the flag-heading scoping) and was cut as a patch +because the PR title had no marker — so its number said "stay as you are" about +a payload the table above says must be re-transferred. It was re-issued as +**`v1.5.0`** with the same template content, and that is the release to +transfer; `v1.4.1` is left in place rather than deleted, because a published +tag is a record. The check that prevents a repeat is mechanical: a PR that +touches any file in the "full re-transfer" row of +`12-template-transfer-air-gapped-network.md` gets `[minor]` in its title +before merging. The rule is repeated at the top of the template's own README, +where whoever edits the template will see it. + ## Reading the version off a published output The tag is where the version is *decided*, but a tag is no use to someone diff --git a/publications/pub-5/template-2026/README.md b/publications/pub-5/template-2026/README.md index 7e5b0e7b..b1b87ddc 100644 --- a/publications/pub-5/template-2026/README.md +++ b/publications/pub-5/template-2026/README.md @@ -12,8 +12,14 @@ template already styled every class pub-10 uses. > **Releases.** Every push to `main` that changes this folder publishes a > versioned zip, tagged `pub-5-template-2026-v..`. Patch is -> automatic; put `[minor]` or `[major]` in a commit message to bump further. -> The release stamps the version into `resources/template-version.txt`, which +> automatic; put `[minor]` or `[major]` in a commit message or PR title to bump +> further. **Any edit to `f13ldman.css`, `notes.css`, the XSLT, the page layouts, +> the fragments or `f13ldMan.opt` is at least `[minor]`** — the transfer +> procedure calls every one of those a full re-transfer, and a patch number +> tells the receiving operator the opposite. Forgetting the marker is easy +> (v1.4.1 was a CSS change cut as a patch, and had to be re-issued as v1.5.0), +> and cheap to check: if the PR touches one of those files, put `[minor]` in +> its title before merging. The release stamps the version into `resources/template-version.txt`, which > Oxygen copies into every published output at > `oxygen-webhelp/template/resources/template-version.txt` — so a publication > can be traced back to the template that built it. That file is committed with