mirror of https://github.com/pnpm/pnpm.git synced 2026-05-12 10:11:42 -04:00

Files

Zoltan Kochan 7bcfd970e9 fix(config): align scoped registry resolution between config get and publish (#11494 )

Fixes [#11492](https://github.com/pnpm/pnpm/issues/11492).

In pnpm v11 a scoped registry resolved to different URLs depending on which command read it:

- `pnpm config get @<scope>:registry` returned the value from `.npmrc`
- `pnpm publish` used the value from `pnpm-workspace.yaml`'s `registries` block

When the two sources disagreed, `pnpm publish` silently targeted the URL from `pnpm-workspace.yaml`, even though `pnpm config get` reported a different (and seemingly authoritative) URL — so users could publish to the wrong registry without any indication.

This PR makes `pnpm config get @<scope>:registry` read from the merged `Config.registries` map (the same map `publish` and the resolvers use) before falling back to `authConfig`. Both commands now report and use the same URL.

2026-05-06 17:06:18 +02:00

src

fix(config): allow user-level preferences in global config.yaml (#11477 )

2026-05-06 01:44:46 +02:00

test

fix(config): align scoped registry resolution between config get and publish (#11494 )

2026-05-06 17:06:18 +02:00

CHANGELOG.md

chore(release): 11.0.6

2026-05-05 19:50:32 +02:00

package.json

chore(release): 11.0.6

2026-05-05 19:50:32 +02:00

README.md

docs: fix package names in README files (#11409 )

2026-04-30 22:59:17 +02:00

tsconfig.json

…

tsconfig.lint.json

…

README.md

@pnpm/config.reader

Gets configuration options for pnpm

Installation

pnpm add @pnpm/config.reader

Usage

import { getConfig } from '@pnpm/config.reader'

getConfig().then(pnpmConfig => console.log(pnpmConfig))

License

MIT