NPM: Add npmTags() to provide full control over which tags are used

[scottgonzalez]

Fixes gh-29
Fixes gh-30

I'd like to have @jquery/core verify that this addresses their needs for handling 1.x/2.x simultaneous releases by overriding npmTags() on the 1.x-master branch.

[dmethvin]

Seems like we'd still end up with latest tagged wrong if we released 2.x and 1.x in that order?

[scottgonzalez]

You'd never tag 1.x as latest.

[dmethvin]

Okay, I was confused about npm's nomenclature for "tag", the version is handled separately. LGTM then.

[mgol]

LGTM.

[jzaefferer]

I just did a test run with QUnit, without any modifications in the release script, and it would run these commands:

npm publish --tag latest
npm tag qunitjs@1.14.1 beta

Still need to verify that setting custom tags works properly as well.

[jzaefferer]

PR for Core: jquery/jquery#1553

[mgol]

Sorry, only now did I see the README entry: Every release must contain at least one tag. Why is that? Currently we don't apply any tags to jQuery 1.x.

[gnarf]

The release number itself is the tag yeah?

[scottgonzalez]

Sorry, only now did I see the README entry: Every release must contain at least one tag. Why is that? Currently we don't apply any tags to jQuery 1.x.

It's a requirement of npm; you cannot publish without a tag.

[mgol]

Sorry, only now did I see the README entry: Every release must contain at least one tag. Why is that? Currently we don't apply any tags to jQuery 1.x.

It's a requirement of npm; you cannot publish without a tag.

Yet another reason for us to create a 1.x tag.

[scottgonzalez]

Yet another reason for us to create a 1.x tag.

There's already a PR for that: jquery/jquery#1553