nx выдает ошибку в рандомном порядке
 

Добрый день, подскажите, может кто сталкивался с таким?
Ошибка появляется примерно после 5 комитов в новую ветку, затем чтобы решить проблему нужно подмержить основную ветку, снова. есть 5 комитов, после чего возникает ошибка

В какую сторону смотреть, где искать проблему?

npm run conditional:lint�

> project@0.0.0 conditional:lint /builds/frontend/project
> node ./tools/scripts/conditional --lint

> project@0.0.0 nx /builds/frontend/project
> nx "affected:dep-graph" "--base=origin/dev" "--file=./tmp/affected.json"

nx affected:dep-graph

Graph dependencies affected by changes

Run command using --base=[SHA1] (affected by the committed, uncommitted and
untracked changes):
--base Base of the current branch (usually master) [string]

or using --base=[SHA1] --head=[SHA2] (affected by the committed changes):
--base Base of the current branch (usually master) [string]
--head Latest commit of the current branch (usually HEAD) [string]

or using:
--files Change the way Nx is calculating the affected command by
providing directly changed files, list of files delimited by
commas [array]
--uncommitted Uncommitted changes [boolean]
--untracked Untracked changes [boolean]

Options:
--help Show help [boolean]
--version Show version number [boolean]
--file output file (e.g. --file=output.json or
--file=dep-graph.html) [string]
--focus Use to show the dependency graph for a particular project and
every node that is either an ancestor or a descendant.
[string]
--exclude Exclude certain projects from being processed
[array] [default: []]
--groupByFolder Group projects by folder in dependency graph [boolean]
--host Bind the dep graph server to a specific ip address. [string]
--port Bind the dep graph server to a specific port. [number]
--all All projects [boolean]
--runner This is the name of the tasks runner configured in nx.json
[string]
--skip-nx-cache Rerun the tasks even when the results are available in the
cache [boolean] [default: false]
--configuration This is the configuration to use when performing tasks on
projects [string]
--only-failed Isolate projects which previously failed
[boolean] [default: false]
--verbose Print additional error stack trace on failure

Error: Command failed: git merge-base --fork-point "origin/dev" "HEAD"
at checkExecSyncError (child_process.js:635:11)
at Object.execSync (child_process.js:671:15)
at getFilesUsingBaseAndHead (/builds/frontend/project/node_modules/@nrwl/workspace/src/command-line/shared.js:55:37)
at Object.parseFiles (/builds/frontend/project/node_modules/@nrwl/workspace/src/command-line/shared.js:31:20)
at Object.<anonymous> (/builds/frontend/project/node_modules/@nrwl/workspace/src/command-line/affected.js:26:112)
at Generator.next (<anonymous>)
at fulfilled (/builds/frontend/project/node_modules/tslib/tslib.js:114:62) {
status: 1,
signal: null,
output: [ null, <Buffer >, <Buffer > ],
pid: 73,
stdout: <Buffer >,
stderr: <Buffer >
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! project@0.0.0 nx: `nx "affected:dep-graph" "--base=origin/dev" "--file=./tmp/affected.json"`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the project@0.0.0 nx script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2021-07-08T09_10_26_538Z-debug.log
child_process.js:674
throw err;
^

Error: Command failed: npm run nx affected:dep-graph -- --base=origin/dev --file=./tmp/affected.json
at checkExecSyncError (child_process.js:635:11)
at execSync (child_process.js:671:15)
at Object.<anonymous> (/builds/frontend/project/tools/scripts/conditional.js:49:1)
at Module._compile (internal/modules/cjs/loader.js:999:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
at Module.load (internal/modules/cjs/loader.js:863:32)
at Function.Module._load (internal/modules/cjs/loader.js:708:14)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:60:12)
at internal/main/run_main_module.js:17:47 {
status: 1,
signal: null,
output: [ null, null, null ],
pid: 30,
stdout: null,
stderr: null
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! project@0.0.0 conditional:lint: `node ./tools/scripts/conditional --lint`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the project@0.0.0 conditional:lint script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2021-07-08T09_10_26_594Z-debug.log