fix: clarify sync step

Author: rcarcasses

.github/workflows/release.yml

@@ -27,14 +27,18 @@ jobs:
 
             Once merged, Release Please will tag `v${version}` and publish the GitHub release automatically.
       - name: Enrich release notes with install instructions
-        if: steps.release.outputs.release_created == 'true'
+        if: always()
         env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           TAG_NAME: ${{ steps.release.outputs.tag_name }}
           VERSION: ${{ steps.release.outputs.version }}
           REPOSITORY: ${{ github.repository }}
         run: |
           set -euo pipefail
+          if [ "${{ steps.release.outputs.release_created }}" != "true" ]; then
+            echo "No release created, skipping note enrichment."
+            exit 0
+          fi
 
           TAR_URL="https://github.com/${REPOSITORY}/archive/refs/tags/${TAG_NAME}.tar.gz"
           TMP_ARCHIVE="$(mktemp)"

README.md

@@ -51,4 +51,4 @@ Once changes land on `main`, the GitHub action opens a release PR. Merging that
 
 If you need to double-check a release manually, re-run the `Release Please` workflow from the Actions tab; it will only open a new PR when there are user-facing commits since the last tag.
 
-Use `bazel sync` after upgrading to ensure the Syft toolchain archives download for your host platform.
+Use `bazel sync` after upgrading to ensure the Syft toolchain archives download for your host platform; this refreshes the Syft binaries for the host OS/architecture.