[fiws]

Summary

• select the npm dist-tag from the package version
• publish prereleases under next and stable releases under latest
• ignore build metadata when detecting prerelease versions

Verification

• actionlint .github/workflows/*.yml
• pnpm publish --dry-run --tag next --no-git-checks

---

Note

Low Risk
CI-only release wiring; no runtime or package code changes, though a wrong tag choice could mislabel a release on npm.

Overview
The publish workflow no longer runs a bare pnpm publish, which always used npm’s default latest tag.

It now reads package.json version, strips build metadata after +, and sets next when the version contains a prerelease segment (e.g. 0.8.0-1) or latest for stable semver. Publish runs with pnpm publish --tag <chosen> --no-git-checks.

^{Reviewed by Cursor Bugbot for commit bf60e9a. Bugbot is set up for automated code reviews on this repo. Configure here.}

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/effect-playwright@bf60e9a

commit: bf60e9a