Remove broken version/re-publish previous version

[nranas]

We need a way to revert to a previous version in the case where we create a broken version.

[nranas]

I think the simplest way to revert to a previous version for our users is to move the latest tag to the version we want to revert to. The version with the latest tag is the one that will be fetched for everyone including the client without specifying any particular version. When this client gets more mature and more users we might want to consider using some kind of beta or next tag for new releases to further improve stability (see blog-post linked below for more information).

• npm dist-tag
• Using npm's package distribution tags to ship stable releases

[nranas]

We will need authorization in the npm account to be able to continue with this. @hfjallemark, please advise.

[hfjallemark]

Everyone who should have access to npm needs to create an account. Let me know your users names and I will add everyone as collaborators.

[nranas]

My username is nranas

//cc @robcar @magahl @Edgar-Cordova @sbochoa @Diego-T

[magahl]

My username is magahl

[robcar]

And mine is robinc

[hfjallemark]

Added.

[nranas]

I can confirm that this works now. To move the latest tag to a different version you would run the following command from the console: npm dist-tag add cignium-hypermedia-client@<version> latest where <version> is the version you want to set as the latest.