Version lookup ignores configured npm registry

[bbartels]

Description

The script in packages/script/src/index.ts hardcodes https://registry.npmjs.org when fetching the latest published version to calculate the next version number.

This ignores the user's npm configuration, making it impossible to build in airgapped environments or when using an internal npm mirror.

Expected behavior

Script should respect the user's configured npm registry via npm_config_registry env var (standard npm/bun behavior).

Current behavior

Always fetches from https://registry.npmjs.org regardless of npm configuration.

Plugins

No response

OpenCode version

No response

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• [FEATURE]:Build script ignores OPENCODE_MODELS_URL env var #11385: Build script ignores OPENCODE_MODELS_URL env var - similar hardcoded registry issue but for models.dev
• [FEATURE]: Add option to disable models.dev fetch for corporate proxy environments #4959: Add option to disable models.dev fetch for corporate proxy environments - related feature request for airgapped/corporate environments
• Suppport for airgapped installation #2224: Support for airgapped installation - broader context about airgapped environment support

Both #11387 and #11385 follow the same pattern: hardcoded external URLs that ignore user configuration. They could potentially be addressed together as part of a broader configuration/environment variable support improvement.

Feel free to ignore if your specific use case differs from these issues.

[github-actions]

To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.

[njimenezotto]

@bbartels This issue also appears when installing plugins from private repositories. npmrc file is completely ignored. Is your PR also fixing that case? Thanks