From 39f30d74e1ee7fa5129045a6fbad2d1c1b2f87dd Mon Sep 17 00:00:00 2001 From: Brandur Date: Wed, 7 Oct 2026 11:51:07 -0500 Subject: [PATCH] Use `pnpm login` for JS release instructions Tiny change to use `pnpm` for the `login` subcommand like we use for `pnpm` for everything else. --- js/docs/development.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/js/docs/development.md b/js/docs/development.md index b086d9c77..4951a28e1 100644 --- a/js/docs/development.md +++ b/js/docs/development.md @@ -248,14 +248,14 @@ Run this section's commands from the repository root. The eight publishable pack ```shell test "$(git rev-parse HEAD)" = "$(git rev-parse "js/v$VERSION^{commit}")" - npm login + pnpm login pnpm -C js install --frozen-lockfile pnpm -C js run build:all for package in js js/migrate js/driver/pg js/driver/prisma js/driver/sqlite js/worker-threads js/test js/cli; do - pnpm -C "$package" publish --access public --tag latest --provenance=false || break + (cd "$package" && pnpm publish --access public --no-git-checks --tag latest --provenance=false) || break done ``` - Complete npm's authentication prompts as needed. Publish packages individually because pnpm 10.22.0's recursive publication does not forward `--provenance=false` to npm. The loop publishes dependencies first and stops on failure; after a partial publication, remove the already-published packages from the loop before rerunning it. For a prerelease, use `--tag next` instead of `--tag latest`. + Complete npm's authentication prompts as needed. Publish packages individually because pnpm 10.22.0's recursive publication does not forward `--provenance=false` to npm. Run publication inside each package directory: `pnpm -C "$package" publish` in this version forwards extra arguments to npm and fails with `EUSAGE`. The loop publishes dependencies first and stops on failure; after a partial publication, remove the already-published packages from the loop before rerunning it. For a prerelease, use `--tag next` instead of `--tag latest`. 7. Once all eight packages are published, create a [GitHub release](https://github.com/riverqueue/river/releases/new) for `js/v$VERSION` and copy the version's `js/CHANGELOG.md` notes into its body. Mark alpha, beta, and RC versions as prereleases.