NotificationsYou must be signed in to change notification settings
Fork1.2k
Star32.1k

fix(catalogs): preserve existing semver ranges when adding packages with`--save-catalog`#9762

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Jump to bottom

Draft

ryo-manba wants to merge1 commit intopnpm:main

base:main

Choose a base branch

fromryo-manba:fix-catalog-semver-preservation

Draft

fix(catalogs): preserve existing semver ranges when adding packages with`--save-catalog`#9762

ryo-manba wants to merge1 commit intopnpm:mainfromryo-manba:fix-catalog-semver-preservation

Conversation

Copy link

ryo-manba commentedJul 15, 2025

When adding a package with--save-catalog to multiple projects in a workspace, the existing catalog entry's semver range (e.g.,^1.0.1) was being replaced with a fixed version (e.g.,1.0.1).

This fix checks for existing catalog entries before updating them.

Fixes#9759

fix(catalogs): preserve existing semver ranges when adding packages w…

33da59c

…ith --save-catalogWhen adding a package with `--save-catalog` to multiple projects in a workspace,the existing catalog entry's semver range (e.g., `^1.0.1`) was being replacedwith a fixed version (e.g., `1.0.1`).This fix checks for existing catalog entries before updating them, ensuring thatcatalog entries maintain their version flexibility across all projects in theworkspace.Fixespnpm#9759