feat(release): ignore project scope for version bump

[Mheaus]

Current Behavior

Since Nx 22, when using conventional commits with independent project relationships, commits affecting a project require the scope to match the project name to apply the full semver bump.

For example:

• feat(my-lib): new feature → minor bump for my-lib ✅
• feat: new feature → minor bump for affected projects ✅
• feat(random-scope): new feature → patch bump (downgraded) ❌

This behavior forces teams to use project names as scopes, which may not align with their preferred commit conventions (e.g., feature-based or functional scopes like feat(auth): ..., feat(ui): ...).

The changelog generation correctly identifies breaking changes regardless of scope matching, but the versioning logic downgrades non-matching scoped commits to patch bumps.

Expected Behavior

With the new ignoreProjectScopeForVersionBump configuration option, teams can opt-in to use commit scopes freely without being constrained to match project names.

When ignoreProjectScopeForVersionBump: true is set in the conventional commits configuration:

• feat(random-scope): new feature → minor bump ✅
• fix(whatever): bug fix → patch bump ✅
• feat(auth)!: breaking change → major bump ✅

The versioning will be based solely on the commit type (feat, fix, etc.) and breaking change indicators, not on scope matching.

Configuration Example

{
  "release": {
    "version": {
      "conventionalCommits": true
    },
    "conventionalCommits": {
      "ignoreProjectScopeForVersionBump": true
    }
  }
}

Related Issue(s)

Fixes #33686

Implementation Details

• Added ignoreProjectScopeForVersionBump boolean option to NxReleaseConventionalCommitsConfiguration
• Modified determineSemverChange() to respect this configuration when determining version bumps
• Added default value (false) to maintain backward compatibility
• Added comprehensive unit tests to validate the new behavior
• Updated type definitions and documentation

[netlify]

👷 Deploy request for nx-docs pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	f714839

[vercel]

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

Project	Deployment	Review	Updated (UTC)
nx-dev	Ready	Preview	Dec 29, 2025 10:37am

[Mheaus]

Hi @Coly010, I'm working for a company that uses this format in their commit messages: type(#123456-project): commit message

We noticed during last week that we didn't have a minor release since our last upgrade to Nx 22 and came to look into it.

I think this condition in shared.ts introduced in #32915 is the root cause for this behavior:

if (
  commit.scope === projectName ||
  commit.scope.split(',').includes(projectName) ||
  !commit.scope
) {

This is my first PR to nx so don't hesitate to tell me if I'm missing anything.
Maybe I can also update some documentation somewhere too.