From 41a741c96e52435fe3f202171ce3f094424a2d36 Mon Sep 17 00:00:00 2001 From: Thomas Date: Sat, 7 Nov 2026 17:55:37 -0500 Subject: [PATCH] Only add package revisions for fixes users will notice --- docs/publishing.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/publishing.md b/docs/publishing.md index 12edb5c..250581e 100644 --- a/docs/publishing.md +++ b/docs/publishing.md @@ -8,9 +8,11 @@ the release tag and matching commit in `flatpak/modules/t3code.yml` and adds the release to `flatpak/com.t3tools.t3code.metainfo.xml`. Refresh the numbered patches in `patches/` before merging. -For packaging updates without a new upstream release, append a hyphen and -package revision to the upstream version in AppStream, such as `0.0.42-2`. -Increment that revision for each packaging release. +For packaging fixes users will notice without a new upstream release, add an +AppStream release that appends a hyphen and package revision to the upstream +version, such as `0.0.42-2`, with a note describing the fix. Increment that +revision for each such release. Changes users won't notice, such as CI or build +tweaks, don't need a release entry. Each release gets its own branch, such as `automation/update-t3code-v0.0.43`. The updater leaves an existing PR for that version alone, so newer releases