fix(auto-version-update): update root package version while publishing

[nutboltu]

Fixes #14985

Root Cause: #14201

In scripts/release/publish-commands scripts we only updated the packages versions and the version in ReactVersion.js. But not the root package version.

Possible Solutions

• Updating the root package version number as per react version.
• Remove version from root package json.

[bvaughn]

I think we should just remove the version field entirely, since it's only in-sync with a few of the packages to begin with. Want to update the PR to do that?

[nutboltu]

@bvaughn I am going to remove version from the package.json

[bvaughn]

Thanks~

[NE-SmallTown]

I don't think we should remove this, because sometimes I want to check the react version on github(not on npm), so if I can't find the version field, it would be confusing

So, IMY, even it's unused, we still need sync the version in the root package.json

[bvaughn]

sometimes I want to check the react version on github(not on npm)

To be honest, that's not really a use case I think we are too worried about supporting, but you can check it here instead:
https://github.com/facebook/react/blob/master/packages/react/package.json#L7

[gaearon]

You can find the version here: https://reactjs.org

Top right corner

[nutboltu]

It's easy to find the version in CHANGELOG.md. Also you can see it in the README

[NE-SmallTown]

Yea, I could find it at many places, changelog, release, package/react/package.json, reactjs.org, even in twitter. But from my perspective, it's a very common case that a open source js project describe it's version in the root package.json, right? I know there are some monorepos like react/babel remove the version, but add it is not a complicate cost, but will give someone a better experience.

But maybe I worry too much :)