fixed release version in pipeline

2026-08-11 15:56:23 +05:00
parent cb39198e0a
commit 3bf2018a62
3 changed files with 20 additions and 12 deletions
@@ -136,10 +136,12 @@ and the composition root in `App.xaml.cs`, which is exercised end-to-end instead
 ## Continuous integration

 The pipelines live in `.gitea/workflows` and run on Gitea Actions. A pull
-request into `master` is built and tested; a tag of the form `v1.2.3.0` is built,
+request into `master` is built and tested; a tag of the form `v1.2.3` is built,
 tested, packed into an MSIX and published as a release with the packages
 attached. The version is taken from the tag alone — a tag shaped any other way
-stops the run right at the start.
+stops the run right at the start. The package version ends up as `1.2.3.0`: the
+Store takes four numbers and keeps the last one for itself, so the tag has no
+say in it.

 Both pipelines ask for a Windows runner labelled `windows-x64` with the .NET 10
 SDK and git-lfs on it. The checkout pulls LFS files: without them the icon is a