Versions not being bumped during release

[dbudwin]

Current Behavior

When I run npx nx release --dry-run it will bump all the versions of dependencies within my packages folder as expected, but is no longer bumping versions for my applications that use these dependencies. I've noticed this regression since upgrading from version 21 to version 22.

Here is my graph of my sample repo. You'll see that my root project nx-bug and my lambda coolLambda both depend on my package test-package.

Expected Behavior

I expect that when a dependency has it's version bumped, the other applications that use that dependency get updated to use that latest version too.

For example, if coolLambda currently uses v1.0.0 of test-package and a change to test-package causes it to become v1.1.0. I expect as part of the release that coolLambda's dependency on testPackage is upgraded from 1.0.0 to 1.1.0.

I don't want to manually bump version numbers in my monorepo when a dependency I manage is upgraded.

GitHub Repo

https://github.com/dbudwin/nx-bug

Steps to Reproduce

1. Clone repo
2. Run pnpm install
3. Make a change to packages/test-package/src/index.js which should trigger a version bump
4. Commit this change using conventional commit syntax (i.e. feat: changed the log statement in the package)
5. Run npx nx release --dry-run

You should see output similar to the following where it bumps the version number of the package, but not of either of the 2 applications that are using it.

npx nx release --dry-run

 NX   Running release version for project: @dbudwin/test-package

@dbudwin/test-package 🏷️  Resolved the current version as 1.3.0 from git tag "@dbudwin/test-package@1.3.0", based on releaseTagPattern "{projectName}@{version}"
@dbudwin/test-package 📄 Resolved the specifier as "minor" using git history and the conventional commits standard
@dbudwin/test-package ❓ Applied semver relative bump "minor", derived from conventional commits data, to get new version 1.4.0
@dbudwin/test-package ✍️  New version 1.4.0 written to manifest: packages/test-package/package.json

UPDATE packages/test-package/package.json [dry-run]

    "name": "@dbudwin/test-package",
-   "version": "1.3.0",
+   "version": "1.4.0",
    "main": "./src/index.js",

 NX   Updating pnpm lock file

 NX   Staging changed files with git

 NX   Previewing an entry in packages/test-package/CHANGELOG.md for @dbudwin/test-package@1.4.0

UPDATE packages/test-package/CHANGELOG.md [dry-run]

+ ## 1.4.0 (2025-12-07)
+
+ ### ✨ New Features
+
+ - made a change to my package 4 ([4a1f466](https://github.com/dbudwin/nx-bug/commit/4a1f466))
+
  ## 1.3.0 (2025-12-07)

  ### ✨ New Features


 NX   Staging changed files with git


 NX   Committing changes with git


 NX   Tagging commit with git


 NX   Skipped publishing packages.


NOTE: The "dryRun" flag means no changes were made.

Nx Report

npx nx report

 NX   Report complete - copy this into the issue template

Node           : 20.11.1
OS             : darwin-arm64
Native Target  : aarch64-macos
pnpm           : 9.6.0

nx              : 22.0.3
@nx/js          : 22.0.3
@nx/jest        : 22.0.3
@nx/eslint      : 22.0.3
@nx/workspace   : 22.0.3
@nx/cypress     : 22.0.3
@nx/devkit      : 22.0.3
@nx/playwright  : 22.0.3
@nx/storybook   : 22.0.3
@nx/web         : 22.0.3
@nx/webpack     : 22.0.3
typescript      : 5.9.3
---------------------------------------
Registered Plugins:
@nx/eslint/plugin
@nx/storybook/plugin
@nx/webpack/plugin
@nx/jest/plugin
@nx/playwright/plugin
---------------------------------------
Community plugins:
nx-stylelint : 17.1.5
---------------------------------------
Cache Usage: 11.96 MB / 46.04 GB

Failure Logs

Package Manager Version

9.6.0

Operating System

• macOS
• Linux
• Windows
• Other (Please specify)

Additional Information

This functionality used to behave the way I expected. I only noticed it just this week and looking back through logs seems like it stopped when we upgraded from v21 to v22 of Nx.