updating versions (#14)

* updating versions * wrong version lol * Clarify why the 1.3 releases are pegged to the branch, not the latest tag --------- Co-authored-by: Jinna Kiisuo <[email protected]>
kanidm · Dec 17, 2024 · b4adb4c · b4adb4c
1 parent 338fb32
commit b4adb4c
Showing 1 changed file with 7 additions and 2 deletions.
diff --git a/.github/workflows/create-apt-repo.yml b/.github/workflows/create-apt-repo.yml
@@ -16,10 +16,15 @@ jobs:
       fail-fast: false
       matrix:
         category:
+            # Previous stable branch + backport.
+            # NOTICE: This is on purpose pointing to the 1.3.0 _branch_ which contains 1.3.3.
+            # The v1.3.3 tag does _not_ include the necessary backport for cargo-deb to function.
+            # This anomaly can be removed once we drop support for 1.3.3.
           - name: stable
-            ref: 1.3.0  # Previous stable branch + backport
+            ref: 1.3.0
+            # While the repo is in "dirty hack" mode, we only publish the latest patch of every minor version.
           - name: stable
-            ref: v1.4.1
+            ref: v1.4.4
           - name: nightly
             ref: master
         os: