Docs: add parallel=1

[edbzn]

OK I guess posting this issue helped me on finding the solution!

I just added parallel=1 to the command.

It would be nice to mention this in the documentation as I guess this is a common use case.

Originally posted by @christophediprima in #414 (comment)

[dereekb]

I ran into this and had some trouble figuring out where exactly to put the command. If you're going to use it inline with the run command, make sure you put it after run and before your nx target:

npx nx run --parallel=1 workspace:version

Here's the other example using this argument within nx.json:

semver/nx.json

Line 27 in 9c2047b

"parallel": 1

[edbzn]

@dereekb would you want to contribute on this?

[dereekb]

Sure, why not. I'll work on a small writeup to add to the docs and make a PR.

[subhranshudas]

i m curious, does this happen all the time? i have seen this happen few times but not sure how to repro it.
Mostly it happens when i am setting my NX workspace fresh (all packages are 0.0.0) and running the version for the 1st time.

yarn nx affected --target version --base= origin/main~1 --head= HEAD --verbose

and get the following
error-

[dereekb]

I'm still trying to reproduce the issue myself, since it pops up occasionally in my CI even with it inline.

Right now I'm having doubts as to whether or not "parallel" changes the behavior at all, or with what runners does it change the behavior, or if it only affects certain commands, such as nx run-many.

One possible guess is here:

semver/packages/semver/src/executors/version/version.ts

Line 86 in 2d72467

concatMap((packageFiles) =>

There might be a race condition with performing concurrent addToStage() since we're using concatMap, so each project is still being updated in parallel. It's hard to reproduce though, but if the changes at addToStage were performed sequentially it might help in my case.

In your case, my guess is that the addToStage() from updating the changeLogs and updating the packageJson hit at the same time, since those are also done in parallel:

semver/packages/semver/src/executors/version/version.ts

Line 54 in 2d72467

return forkJoin([

[hellraisercenobit]

Same behavior like @subhranshudas since v2.23.4 with or without parallel=1 and syncVersions to true.

[edbzn]

Seems like the refactoring to get rid of standard-version introduced this issue, but I'm wondering why e2e tests don't catch anything, I have never seen this error myself.

[hellraisercenobit]

it's seems it's coming from the trade between concat and forkJoin operators.
i'm not sure about that.