Che Theia release script should get upstream Theia version from yarn.lock or npmjs.org

[azatsarynnyy]

Is your enhancement related to a problem? Please describe.

Currently, Che Theia release script reads upstream Theia version from THEIA_VERSION file that has to be manually updated in master branch before doing a release.
We should avoid this manual update.

Describe the solution you'd like

It can be automated by reading it from yarn.lock file.

Describe alternatives you've considered

It can be automated by reading it from npmjs.org.

Additional context

[benoitf]

Hi

I was thinking that it could be nice is that if ./build.sh could

• by default (or with a flag) grab the current “upstream tag” by looking at npmjs for the next1.1.0-next.669ad8b7 version
• have a way to specify this version so that we can easily build theia using a previous sha1
• release mode where we use for example THEIA_VERSION or in that case yarn.lock @theia/core.

so let say someone is blocked with current upstream, he can used a previous tag easily like
./build.sh --upstream-commit-tag 66dd2bc6
and then that we don’t have to provide git-refs stuff, THEIA_VERSION , --branch or git-refs on build.sh script (all being handled)

then make-release would just call build.sh or something different

[benoitf]

to grab from npmjs:

$ curl --silent http://registry.npmjs.org/-/package/@theia/core/dist-tags | sed 's/.*"next":"\(.*\)".*/\1/'
1.1.0-next.669ad8b7

[azatsarynnyy]

good idea to parametrize upstream version
I'll work on it. Thx!