Skip to content

Commit 90f30b7

Browse files
committed
ci(release): publish under the 'bridge' dist-tag
The version carries a semver prerelease segment (6.0.3-bridge.0…), and npm rejects publishing prereleases to the implicit latest tag — the publish job failed on the first sub-package with 'You must specify a tag'. Pin both the sub-package loop and the main publish to --tag bridge; installs go through npm i typescript-native-bridge@bridge or by exact version, and latest stays free for a future stable line.
1 parent cbf1210 commit 90f30b7

1 file changed

Lines changed: 4 additions & 2 deletions

File tree

‎.github/workflows/release.yml‎

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -173,14 +173,16 @@ jobs:
173173
set -euo pipefail
174174
for d in subpkgs/*; do
175175
echo "== publishing $(basename "$d") =="
176-
(cd "$d" && npm publish --provenance)
176+
(cd "$d" && npm publish --provenance --tag bridge)
177177
done
178178
env:
179179
# Empty when the secret is unset: npm then falls back to OIDC trusted publishing.
180180
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
181181

182182
- name: Publish main package
183-
run: npm publish --provenance
183+
# --tag bridge: the version is a semver prerelease (x.y.z-bridge.N…);
184+
# npm refuses to publish prereleases to the implicit `latest` tag.
185+
run: npm publish --provenance --tag bridge
184186
working-directory: staging
185187
env:
186188
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

0 commit comments

Comments
 (0)