fix(release): handle short and full project names in commit scopes

[ShwethaSundar]

Current Behavior

Conventional commit scopes must exactly match the Nx project name.
If a commit uses a short scope (e.g. commons2) while the project name is fully qualified (e.g. @commons/commons2), the commit is treated as not project-scoped. This causes incorrect semver bumps, sometimes affecting multiple projects.

Expected Behavior

Commit scopes should match projects using either:

• Full project name (@commons/commons2)
• Short name (commons2)
• Comma-separated scopes using either form

Related Issue(s)

Fixes #

[netlify]

👷 Deploy request for nx-docs pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	de2b402

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
nx-dev	Ready	Preview	Feb 3, 2026 5:17am

[ShwethaSundar]

@leosvelperez @Coly010 Could you please review this MR?

[netlify]

👷 Deploy request for nx-dev pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	de2b402

[ShwethaSundar]

@Coly010 @leosvelperez Could I get a review please?

[JamesHenry]

@ShwethaSundar I'm a bit uneasy with the ad hoc matching logic here in general... can we please integrate the findMatchingProjects utility that is used throughout most of the nx codebase? It should handle the short name matching consistently with the task runner

[nx-cloud]

View your CI Pipeline Execution ↗ for commit b410b91

Command	Status	Duration	Result
nx affected --targets=lint,test,test-kt,build,e...	❌ Failed	51m 30s	View ↗
nx run-many -t check-imports check-lock-files c...	✅ Succeeded	4m 12s	View ↗
nx-cloud record -- nx-cloud conformance:check	✅ Succeeded	7s	View ↗
nx-cloud record -- nx format:check	✅ Succeeded	2s	View ↗
nx-cloud record -- nx sync:check	✅ Succeeded	<1s	View ↗

---

☁️ Nx Cloud last updated this comment at 2026-02-13 09:36:52 UTC

[nx-cloud]

Nx Cloud is proposing a fix for your failed CI:

These changes fix the module resolution error that was causing all e2e-release tests to fail. We corrected the import path from an absolute-style path to a relative path (../../../utils/find-matching-projects), which aligns with the existing import patterns in the file and allows Node.js to properly resolve the module.

Warning

❌ We could not verify this fix.

diff --git a/packages/nx/src/command-line/release/utils/shared.ts b/packages/nx/src/command-line/release/utils/shared.ts
index bc56d46675..347d59b6ed 100644
--- a/packages/nx/src/command-line/release/utils/shared.ts
+++ b/packages/nx/src/command-line/release/utils/shared.ts
@@ -14,7 +14,7 @@ import {
   gitCommit,
   sanitizeProjectNameForGitTag,
 } from './git';
-import { findMatchingProjects } from 'packages/nx/src/utils/find-matching-projects';
+import { findMatchingProjects } from '../../../utils/find-matching-projects';
 import { ReleaseGraph } from './release-graph';
 
 export const noDiffInChangelogMessage = pc.yellow(

Because this branch comes from a fork, it is not possible for us to apply fixes directly, but you can apply the changes locally using the available options below.

Apply changes locally with:

npx nx-cloud apply-locally Ih60-sZ3q

Apply fix locally with your editor ↗   View interactive diff ↗

_{🎓 Learn more about Self-Healing CI on nx.dev}

[JamesHenry]

@ShwethaSundar just checking you saw the failing CI and suggested fix?

[ShwethaSundar]

@ShwethaSundar just checking you saw the failing CI and suggested fix?

yes its fixed.