`nx release`: changelog of independent project include workspace changes about nx HOT 2 OPEN

@Badisi if your commit convention allows you to use other types than fix or feat you can configure your nx release command to ignore certain types of commits when the release command needs to determine the next version.

See the documentation here: https://nx.dev/recipes/nx-release/customize-conventional-commit-types

A change to non-projects files can always be affecting other projects. I believe this is a safe approach as it leaves it to the developer to use commit types such as chore or test to mark a commit to be 'hidden' in your changelog and not cause any version bump.

from nx.

@thdk, I'm using the default commit convention, nothing fancy here.

My real concern is that when using independent mode and projectChangelogs level, changelogs should only be scoped to a project level and not include any workspace changes.

And that's actually what the documentation says:

... they are generated for each project individually and only contain changes for that specific project ...

So in this particular scenario I completely disagree with you when you say that "a change to non-projects files can always be affecting other projects". The idea behind projectChangelogs is purposely to ignore any changes that was made outside of a project scope and only include what was made inside it.

As for commit types such as chore or test, I agree they can help 'hide' a commit but it's just a dirty solution here and does not completely solves the problem. To err is human, and you can't depend on a developer always remembering to use the correct commit types to ensure proper scoping or exclusion within a project.

from nx.