ci: report Build & canary release once, and skip the canary on release PRs

.changeset/tidy-release-checks.md

@@ -0,0 +1,5 @@
+---
+'@cube-dev/ui-kit': patch
+---
+
+Release-pipeline maintenance, no runtime changes: the `Build & canary release` check is no longer reported twice by two different workflows, and the Version Packages PR no longer publishes a redundant canary or leaves a stale `pr_*` dist-tag behind.

.github/workflows/publish.yml

@@ -81,7 +81,13 @@ jobs:
       - name: Clear .npmrc auth token (use OIDC instead)
         run: npm config delete //registry.npmjs.org/:_authToken || true
 
+      # The Version Packages PR changes nothing but the version and changelog,
+      # so a canary of it would be a duplicate of what `main` already published
+      # and would leave another stale `pr_*` dist-tag behind. The job itself
+      # still runs so the required `Build & canary release` check reports, and
+      # the build above still verifies the exact tree that is about to ship.
       - name: Publish canary to npm
+        if: github.head_ref != 'changeset-release/main'
         env:
           CANARY_VERSION: ${{ steps.version.outputs.version }}
           PR_TAG: pr_${{ github.event.number }}
@@ -94,6 +100,7 @@ jobs:
           fi
 
       - name: Comment PR
+        if: github.head_ref != 'changeset-release/main'
         uses: actions/github-script@v6
         with:
           github-token: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/pull-request.yml

@@ -18,15 +18,6 @@ permissions:
 # Note: Canary publishing is handled by publish.yml workflow
 
 jobs:
-  # This job exists only to satisfy branch protection rules that expect this check name
-  # The actual publishing is done in publish.yml
-  build-canary-status:
-    name: 'Build & canary release'
-    runs-on: ubuntu-latest
-    steps:
-      - name: Publishing handled by publish.yml
-        run: echo "Canary publishing is handled by the Publish workflow (publish.yml)"
-
   tests:
     name: 'Tests & lint'
     runs-on: ubuntu-latest