Given I have a package named `jon` at version `0.1.0-a`
And I call `npm publish --tag=next`
Then I expect `npm dist-tag ls jon` to show `next: 0.1.0-a`
instead it publishes without error.
To work around, I call `npm dist-tag add email@example.com next`
My word around doesn't include setting the `latest` tag back to the appropriate version (`latest` should not update when using `--tag` with `npm publish`)
Note, the workaround wasn't available until 4.1 thanks to https://www.jfrog.com/jira/browse/RTFACT-7400