Previously hotfix releases on old stable branches used to automatically publish with latest, which overwrote the tag for the actual latest release.
https://github.com/facebook/metro/pull/1086 attempted to fix that, and mostly works, but npm does not allow dist tags that pass semver.isValid(), because that would conflict with semver specifiers in package@[tagorsemver]. Our stable branch naming convention 0.76.x happens to be valid semver, and is rejected as a tag name.
This uses 0.76-stable instead via shell substitution. I've just used it to semi-manually successfully publish 0.76.9.
Summary
Previously hotfix releases on old stable branches used to automatically publish with
latest, which overwrote the tag for the actual latest release.https://github.com/facebook/metro/pull/1086 attempted to fix that, and mostly works, but npm does not allow dist tags that pass
semver.isValid(), because that would conflict with semver specifiers inpackage@[tagorsemver]. Our stable branch naming convention0.76.xhappens to be valid semver, and is rejected as a tag name.This uses
0.76-stableinstead via shell substitution. I've just used it to semi-manually successfully publish 0.76.9.Test plan
0.76-stable