Return to maintaining a "next" or "dev" dist-tag on npm? #4110
Description
Up until recently, there was an npm 'dist-tag' that someone was regularly updating to pint to the next -dev.* version of bs-platform. This was super-useful for CI scripts (like, mine) and allowed projects to have a "canary" build that fails before end-users start to see failures.
For some reason, it looks like the "dev" dist-tag has disappeared from npm:
(Also, why are we creating dist-tags for each version? That seems ... odd; and could possibly result in a specific version being swapped out from under a user's feet accidentally!)
This was, of course, never documented; so I'm not gonna be super-offended if nobody wants to update the publishing-scripts to maintain a tag ... but I'd point out that this could be helpful in improving the software-health of the overall ecosystem! (=