From 44da7af3a2e4cbc5d76953a2cb70d47bac20aa9a Mon Sep 17 00:00:00 2001 From: Jakub Kasprzyk Date: Tue, 27 Oct 2026 22:55:10 +0100 Subject: [PATCH] ci: log npm's publish result in the Release workflow MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit release-it in --ci mode hid npm's output, so the 0.1.0 run showed only "✔ npm publish" while the version took about 5 minutes to appear on the registry. Run release-it with -VV, which logs the output of its own commands, including npm's "+ @" once the registry accepts the package. -V (--verbose) only logs hook output. npm's notices go to stderr, which release-it shows only when a command fails. RELEASING.md says the version can take a few minutes to show up and not to re-run the workflow or re-tag meanwhile. --- .github/workflows/release.yml | 6 +++++- RELEASING.md | 5 +++++ 2 files changed, 10 insertions(+), 1 deletion(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 21a2cd1..d2204c7 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -131,7 +131,11 @@ jobs: # --no-increment: the version already lives in package.json, reviewed # and merged through a pull request. # --no-git: the tag is pushed by the maintainer; CI never writes to git. - args=(--ci --no-increment --no-git) + # -VV: logs the output of release-it's own commands, including npm's + # `+ @` once the registry accepts the package. `-V` + # only logs hook output. npm's notices go to stderr, which release-it + # shows only when a command fails. + args=(--ci --no-increment --no-git -VV) if [ "${{ github.event_name }}" != 'push' ]; then args+=(--dry-run) echo 'Rehearsal run — nothing will be tagged or published.' diff --git a/RELEASING.md b/RELEASING.md index 4f0df78..80e2ef8 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -50,6 +50,11 @@ version is not already on npm and that `CHANGELOG.md` has a section for it; publishes to npm with provenance; and creates the GitHub Release with that section as its body. +The Publish step logs `+ @gmisoftware/react-native-pay@` when npm +accepts the package. The version can take a few minutes more to show up on the +registry: 0.1.0 appeared about 5 minutes after the workflow finished. Don't +re-run the workflow or re-push the tag while you wait. + The iOS podspec reads its version from `package.json`, so there is no second version to keep in sync.