You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I am having issue with nx release not detecting changes (No changes were detected using git history and the conventional commits standard.) when upgrading dependencies in root package.json and using scoped commit.
Steps to reproduce
bump dependency in root package.json,
stage the changes (the only changed files workspace-root package.json and lock-file
commit the changes as feat(deps): bump testing dependencies or feat(repo): bump testing dependencies.
build the projects as npx nx affected --target=build - it properly detect changes and build all affected projects (in my case all projects in monorepo)
run nx release - observe no changes were detected message and no new release created.
I tried adding package.json to sharedGlobals in namedInputs but no lock with that
Same changes are released without any issues if the non-scoped commits is used but I am pretty used to adding repo or deps scope to those changes and it seems that is default for renovate updates.
Are there any way to make nx release detect changes or should I fallback to using non-scoped commits?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi, I am having issue with
nx release
not detecting changes (No changes were detected using git history and the conventional commits standard.
) when upgrading dependencies in rootpackage.json
and using scoped commit.Steps to reproduce
package.json
and lock-filefeat(deps): bump testing dependencies
orfeat(repo): bump testing dependencies
.npx nx affected --target=build
- it properly detect changes and build all affected projects (in my case all projects in monorepo)I tried adding
package.json
tosharedGlobals
innamedInputs
but no lock with thatSame changes are released without any issues if the non-scoped commits is used but I am pretty used to adding
repo
ordeps
scope to those changes and it seems that is default forrenovate
updates.Are there any way to make nx release detect changes or should I fallback to using non-scoped commits?
Beta Was this translation helpful? Give feedback.
All reactions