Versions mismatch cause npm error about z-schema

[zaggino]

Hi, unless you're using Node 4.x, you can safely update to z-schema 4.x

[smartmouse]

HI , we ran into the same issue, We cannot upgrade since we have shirnkwrap already/ Is it possible to publish that version. 3.26.0 in npmjs.org
Appreciated your help.

npm WARN deprecated [email protected]: All versions below 4.0.1 of Nodemailer are deprecated. See https://nodemailer.com/status/
npm WARN deprecated [email protected]: No longer maintained, please upgrade to swagger-ui@3.
npm ERR! code ETARGET
npm ERR! notarget No matching version found for [email protected]
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

[rmg]

As far as I can tell, 3.26.0 was unpublished.

Since 3.26.0 was already published once there is no way to re-publish it. The best that could be done is to branch from the 3.26.0 tag and re-publish as 3.26.1.

The problem @smartmouse is reporting is an unfortunate case of generating an npm-shrinkwrap.json between when 3.26.0 was published and when it was unpublished. The use of a private (caching) registry means the unpublish wasn't noticed. In fact, the z-schema-2.26.0.tgz tarball probably still exists on many such registries :-(

Since 3.26.0 exists in caches, I took a quick look at it. I couldn't find any obvious reason to unpublish it (eg. leaked personal information) so I'm guessing it was retracted in favour of just jumping to 4.x. I'm sure @zaggino had no idea that anyone would have installed and pinned to that specific version within the 72 hours (max) that the version existed on npm.

[zaggino]

3.26.0 was published and it broke node v4, by mistake, to not introduce any code-breaks with semver-minor, I've unpublished it

I've also decided to go with 4.0.0 because I don't see a reason to keep supporting so old node versions