ci(release): keep latest in sync with each release

Until now the workflow only moved the bridge tag, so latest would have
drifted back to the 0.0.0 placeholder on the next release (what bit
users in issue #8 before it was fixed manually). After publishing
under --tag bridge, point latest at the same version for the main
package and all seven platform packages; switch the step off when a
stable line takes over latest.

Author: johnsoncodehk

.github/workflows/release.yml

@@ -187,6 +187,20 @@ jobs:
         env:
           NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
 
+      - name: Point latest at the release
+        # The bridge line is the only real content today; keep `latest` in sync
+        # so bare `npm i` never resolves to a stale placeholder (issue #8).
+        # dist-tag add needs no OTP under trusted publishing/OIDC.
+        run: |
+          set -euo pipefail
+          V="$(node -p "require('./staging/package.json').version")"
+          npm dist-tag add "typescript-native-bridge@$V" latest
+          for p in darwin-arm64 darwin-x64 linux-x64 linux-arm64 linux-arm win32-x64 win32-arm64; do
+            npm dist-tag add "@typescript-native-bridge/$p@$V" latest
+          done
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+
       - name: Create GitHub Release
         run: gh release create "${GITHUB_REF_NAME}" --generate-notes --verify-tag
         env: