Skip to content

ci: log npm's publish result in the Release workflow - #59

Merged
jkasprzyk17 merged 1 commit into
mainfrom
ci/release-it-verbose
Nov 4, 2026
Merged

jkasprzyk17 merged 1 commit into
mainfrom
ci/release-it-verbose

Conversation

@jkasprzyk17

@jkasprzyk17 jkasprzyk17 commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • The Release workflow runs release-it with -VV, so the Publish step logs npm's + @gmisoftware/react-native-pay@<version> once the registry accepts the package. In the 0.1.0 run (40587150921) --ci mode showed only ✔ npm publish, and the version took about 5 minutes to appear on the registry.
  • -VV, not --verbose: in release-it, -V/--verbose only logs hook output, and npm publish is one of its own commands, which only -VV logs. npm's npm notice lines (file list, provenance link) go to stderr, which release-it shows only when a command fails. The workflow comment says so.
  • RELEASING.md: the version can take a few minutes to show up after the workflow finishes; don't re-run the workflow or re-push the tag meanwhile.

Test plan

  • actionlint .github/workflows/release.yml: passes
  • Locally, with package/package.json temporarily at 0.1.1-verbosetest.0 (reverted, not committed): GITHUB_TOKEN=$(gh auth token) bunx release-it --ci --no-increment --no-git --dry-run -VV logs + @gmisoftware/react-native-pay@0.1.1-verbosetest.0 after npm publish --dry-run. Without -VV (the 0.1.0 run) that line is missing.
  • Release workflow on the next tag (a rehearsal on main now stops at "already published", since 0.1.0 is on npm)

Risk

  • Log output only. -VV also prints the output of release-it's git and npm queries (git describe, npm view), so the Publish log is longer.

Notes

  • Same gap exists in react-native-better-pdf's release.yml.

View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need.

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 "+ <name>@<version>" 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.
@coderabbitai

coderabbitai Bot commented Oct 27, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

No actionable comments were generated in the recent review.

Recent review info
Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Essentials
  • Run ID: 3bc8357e-ca90-443a-b6c5-b0c94c224a61
Commits

Reviewing files that changed from the base of the PR and between 130df37 and 44da7af.

Files selected for processing: 2
  • .github/workflows/release.yml
  • RELEASING.md

Included review availability: This review used your included allowance. 1 included review remains after this review. Your included PR review attempts over the past 7 days set your current allowance at 2 reviews per hour.

📝 Summary

Summary by CodeRabbit

  • Release Process

    • The release workflow now provides more detailed command and package-publishing output, making its progress easier to follow.
  • Documentation

    • Release guidance notes that an accepted package may take several minutes to appear. It advises waiting rather than rerunning the workflow or pushing the tag again during that time.

The release workflow now invokes release-it with -VV. The release guide explains how to interpret npm acceptance logs and what to do while the package becomes visible in the registry.

Changes: Release publishing

Layer / File(s) Summary
Release output and publication guidance
.github/workflows/release.yml, RELEASING.md
The workflow adds -VV and updates comments about expected output. The guide explains that registry visibility may take several minutes after npm accepts the package, and instructs maintainers not to rerun the workflow or repush the tag while waiting.

Priority: Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Possibly related PRs

Suggested reviewers: piotr-graczyk-dev

Merge Risk: Minimal · up to 44da7

The workflow adds supported diagnostic output without changing package publication behavior.

Pre-merge checks: Passed 6
Check name Status Explanation
Title check Passed The title is 52 characters, which slightly exceeds the 50-character guideline. It uses the type prefix "ci:" and describes the main change: the Release workflow now logs npm's publish result by runnin…
Description check Passed The description is directly related to the changeset. It explains that the Release workflow now runs release-it with -VV so the Publish step logs npm's package version, gives the reasoning for -VV ove…
Docstring Coverage Passed No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Documentation-only edits and deletions within survi…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Security Check Passed No medium, high, or critical vulnerability is introduced. The only executable change adds release-it -VV to the existing publish step. It logs the package/version result and release-it command outpu…
Full details: Title check

Explanation

The title is 52 characters, which slightly exceeds the 50-character guideline. It uses the type prefix "ci:" and describes the main change: the Release workflow now logs npm's publish result by running release-it with -VV. The title is accurate and specific, so it meets the requirement apart from the minor length overrun.

Full details: Description check

Explanation

The description is directly related to the changeset. It explains that the Release workflow now runs release-it with -VV so the Publish step logs npm's package version, gives the reasoning for -VV over --verbose, records the local dry-run and actionlint checks, lists the remaining unchecked rollout test, and describes the RELEASING.md note about waiting for npm to show the version.

Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)

Full details: Security Check

Explanation

No medium, high, or critical vulnerability is introduced. The only executable change adds release-it -VV to the existing publish step. It logs the package/version result and release-it command output; the reviewed workflow does not pass secrets as command arguments, and the logged values are not sensitive. RELEASING.md contains documentation only. No prior security threads or current findings require re-reporting.

  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Warning

Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption.

Comment @coderabbitai help to get the list of available commands.

@jkasprzyk17
jkasprzyk17 merged commit 3583af7 into main Nov 4, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant