• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

supabase / cli / 29909552003
65%
develop: 65%

Build:
Build:
LAST BUILD BRANCH: pamela/growth-958-cli-surface-entitlement-upgrade-hint-from
DEFAULT BRANCH: develop
Ran 22 Jul 2026 09:52AM UTC
Jobs 1
Files 230
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

22 Jul 2026 09:49AM UTC coverage: 65.289%. Remained the same
29909552003

push

github

web-flow
chore(release): stop mutating global registry config in local-registry (#5922)

## What

`pnpm local-registry` (the local Verdaccio helper for release testing)
no longer redirects the global `npm` and `pnpm` registry config to
`localhost:4873` on startup, and no longer needs to restore it on
shutdown. The cleanup handler now just kills Verdaccio, and additionally
handles `SIGHUP` so closing the terminal window doesn't orphan the
server. `CONTRIBUTING.md` is updated to match, and the troubleshooting
table now covers recovering from the stale override left behind by older
versions of the script.

## Why

The restore path had holes that could leave a developer's machine
pointed at a dead localhost registry, making every subsequent `pnpm i`
fail:

- The Verdaccio-crash path called `process.exit(1)` without restoring
the registry.
- `SIGHUP` (closing the terminal) wasn't handled, so no cleanup ran at
all.
- A partial restore failure only printed a warning, right as the
terminal session was being torn down.

This bit for real: pnpm persists the override in its own global config
(`~/Library/Preferences/pnpm/auth.ini` on macOS) rather than `~/.npmrc`,
so an `~/.npmrc`-focused manual cleanup makes npm look healthy while
pnpm silently keeps resolving from `localhost:4873`.

The global redirect was also unnecessary: `local-release.ts` already
passes `--registry` explicitly to every publish command and writes a
scoped `.npmrc` (with the auth token) into its temp publish dir, and the
suggested `npx` / `npm install -g` smoke-test commands carry the flag
too. With the redirect gone, there is no cleanup left to get wrong — a
crash or hard kill can no longer corrupt the developer's registry
config.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

11250 of 17231 relevant lines covered (65.29%)

10.51 hits per line

Jobs
ID Job ID Ran Files Coverage
1 29909552003.1 22 Jul 2026 09:52AM UTC 230
65.29
GitHub Action Run
Source Files on build 29909552003
  • Tree
  • List 230
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #29909552003
  • e44a2bd4 on github
  • Prev Build on develop (#29909467155)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc