Check for package-version-updated

[sarbull]

Signed-off-by: Sirbu Nicolae-Cezar sirbunicolaecezar@gmail.com

LATER EDIT

Also, we can use this command so that we create a snapshot version in order to prepare a release and it will run the docker pipeline because it will sense a version change, in this way it will start the docker pipeline creating the required image.

/Users/sarbull/awesome-projects/egeria-ui [git::test-branch] [sarbull@my-computer] [17:09]
> npm version prerelease --preid snapshot
v3.1.2-snapshot.0

/Users/sarbull/awesome-projects/egeria-ui [git::test-branch] [sarbull@my-computer] [17:09]
> cat package.json 
{
  "name": "egeria-ui",
  "version": "3.1.2-snapshot.0",
  "description": "Egeria UI application",
....
}

After N number of snapshots when we'll bump the version it will look like this, here is an example of a patch after a couple of snapshots.

/Users/sarbull/awesome-projects/egeria-ui [git::test-branch] [sarbull@my-computer] [10:14]
> npm version patch
v3.1.2

Without version change:

With version change:

[lpalashevski]

The solution seems good to me & most importantly fixes the major image overriding issue we had.
Lets add couple of lines of description in the README Release cycle, explaining the command to do pre-release npm version prerelease --preid snapshot and mention that new container image versions get created for each package.json version change.

[lpalashevski]

Approved (see comment)

[lpalashevski]

Since we are not using release branches this block (61:70) is obsolete and can be removed.

[sarbull]

agree, but let's do that in a different iteration

[planetf1]

Change looks good - We have the ability to do pre-release updates whenever we wish within the development cycle (to align with egeria master for example) as well as keep a stable release.