[QUESTION]: Why are minor updates released with the old minor version number?

[markterrill]

Why aren't minor updates published as minor version increments? The current full "dev.master-xxxxxx" tag negates the ability to setup yarn/npm to fetch and install minor updates or check for outdated packages.

I honestly thought it was a bug in the NPM publishing process, where the 'latest' points to the last (old) major release.

You need to use the full tag to actually get the latest version. Seems the publish process isn't actually publishing as the version number, but is publishing as the version + branch + commit.

A clear and concise description of the problem...

Look at https://www.npmjs.com/package/@ngxs/storage-plugin/v/3.7.3-dev.master-b00eeb3

• @ngxs/storage-plugin@latest installs '3.7.3' tag, which is pointing to old code (https://github.com/ngxs/store/tree/v3.7.3/packages/storage-plugin)
• Master has src files updated 12 months ago. https://github.com/ngxs/store/tree/master/packages/storage-plugin

The wrong version installs if you happen to use @latest or @3.7.3, though works if you use the full dev master tag, ie yarn add @ngxs/storage-plugin@3.7.3-dev.master-b00eeb3

Environment

• Yarn 1.22.15
• Node lts/erbium -> v12.22.12

For Tooling issues:

• Node version: lts/erbium -> v12.22.12
• Platform: Mac