Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[rush] `rush change` does not detect change to catalog version of dependency

Open
#5,624 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
tooling

Research direction

Reproduce the issue using common/config/rush/pnpm-config.json and project-a/package.json with Rush 5.166.0, then trace the rush change entry point for catalog dependency handling. Confirm that changing the global React catalog version is detected and produces a relevant change proposal.

Written by the indexing model from the issue text.

Description

Summary

rush change does not detect change to catalog version of dependency

Setup .e.g.

  1. Create a global catalog entry:
// common/config/rush/pnpm-config.json
...
globalCatalogs": {
    "default": {
      "react": "^18.0.0",
    }
  }
  1. Add catalog entry:
// project-a/package.json
...
dependencies: {
   "react": "catalog:
}

Reproduce .e.g.

  1. Alter "react": "^18.0.0" => "react": "^18.0.1"
  2. Run rush change => No changes were detected to relevant packages on this branch. Nothing to do.

Standard questions

Please answer these questions to help us investigate your issue more quickly:

Question Answer
@microsoft/rush globally installed version? yes
rushVersion from rush.json? 5.166.0
pnpmVersion, npmVersion, or yarnVersion from rush.json? 10.28.2
(if pnpm) useWorkspaces from pnpm-config.json? true
Operating system? Mac
Would you consider contributing a PR? Yes
Node.js version (node -v)? 20.20.0
Dominant language
TypeScript
Stars
6.5k
Forks
708
Avg merge
4d 13h
Merged PRs (30d)
62

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/rushstack

All issues in microsoft/rushstack

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.