skcomms 0.2.5__tar.gz → 0.2.7__tar.gz

{skcomms-0.2.5 → skcomms-0.2.7}/.github/workflows/publish.yml

@@ -47,11 +47,20 @@ jobs:
           git config user.name  "github-actions[bot]"
           git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
 
-          latest="$(git describe --tags --abbrev=0 --match 'v[0-9]*' 2>/dev/null || echo '')"
+          # Use the HIGHEST v-tag in the repo, not `git describe`.
+          #
+          # describe only sees tags that are ANCESTORS of HEAD, so an unpushed,
+          # orphaned or rename-stranded tag makes it report "previous: none" and
+          # restart the sequence from zero. That published skcoord/skdashboard
+          # 0.0.1 and then 0.0.2, both BELOW the existing 0.1.0. A release must
+          # never be able to go backwards, so rank all tags by version instead.
+          latest="$(git tag -l 'v[0-9]*.[0-9]*.[0-9]*' | sort -V | tail -1)"
           head_sha="$(git rev-parse HEAD)"
 
-          if [ -n "$latest" ] && [ "$(git rev-list -n1 "$latest")" = "$head_sha" ]; then
-            echo "HEAD is already $latest; nothing to release."
+          # Any release tag AT HEAD means nothing new to ship, even if it is
+          # not the highest one (ranking means the highest may sit elsewhere).
+          if [ -n "$(git tag --points-at HEAD -l 'v[0-9]*.[0-9]*.[0-9]*')" ]; then
+            echo "HEAD is already tagged; nothing to release."
             echo "tagged=false" >> "$GITHUB_OUTPUT"
             exit 0
           fi
@@ -141,6 +150,15 @@ jobs:
 
   pypi-publish:
     needs: build
+    # Same always() guard the build job needs, one level further down.
+    # GitHub propagates a skip THROUGH a job: `tag` is skipped on the tag-push
+    # path, `build` survives it with always(), but a bare `needs: build` here
+    # still evaluates to skipped, because an ANCESTOR was skipped. The publish
+    # step could then never run on a tag push: the build is green, the run
+    # reports success, and NOTHING is uploaded. skharness lost v0.3.13 to this
+    # exact bug. Ported from skcoord PR #6.
+    if: >-
+      always() && !cancelled() && needs.build.result == 'success'
     runs-on: ubuntu-latest
     environment: pypi
     permissions:

{skcomms-0.2.5/src/skcomms.egg-info → skcomms-0.2.7}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: skcomms
-Version: 0.2.5
+Version: 0.2.7
 Summary: Sovereign communications for AI agents — multi-channel transport + FQID realm addressing
 Author-email: smilinTux <chefboyrdave2.1@gmail.com>
 License: GPL-3.0-or-later

{skcomms-0.2.5 → skcomms-0.2.7/src/skcomms.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: skcomms
-Version: 0.2.5
+Version: 0.2.7
 Summary: Sovereign communications for AI agents — multi-channel transport + FQID realm addressing
 Author-email: smilinTux <chefboyrdave2.1@gmail.com>
 License: GPL-3.0-or-later