support more npm tags

[xavdid-stripe]

Why?

When you release on NPM, you can specify a tag for the release (docs). This lets your users install an alias that points to the latest release in a channel:

npm install package@whatever

Previously, we've tagged everything that wasn't GA with the beta tag. That has two issues:

1. Now that there's private-preview releases, not all non-GA releases are "beta"
2. We're moving away from the beta nomenclature in favor of public-preview

To support this change, we updated the tags we use when publishing. These tags can be any string, so switching them is fine. There's nothing special about the beta tag we were using.

The only downside is that for new users who find docs that still say npm install stripe@beta, they'll now get an older version of the package (since we're not tagging releases with that anymore). If this is an issue, we can likely give a release multiple tags, but I'm not positive. There's no effect on existing users, since people with existing dependency declarations have a real version specifier.

I've called out this change in the changelog.

What?

• swapped a bash regex for a jq command
• add support for the other release channels
• added docs

See Also

• RUN_DEVSDK-1935

Changelog

• Starting with this release, we'll no longer be tagging releases with beta npm tag. Instead, we'll use latest, public-preview, or private-preview to more closely align with Stripe's release phases