You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When `--preid` is provided, the release script uses it as the npm publish tag.
152
-
Without a prerelease preid, the publish tag is `latest`.
153
-
154
-
Push `<my_release_branch>`, open a PR from `<my_release_branch>` to `17.x.x`, wait for CI to pass, merge the PR, and then approve the GitHub Actions release workflow.
152
+
Without a prerelease preid, stable releases from the latest major use the npm
153
+
`latest` tag and are marked as the latest GitHub release. Stable releases from
154
+
older maintained majors use an npm `latest-<major>` tag and are explicitly not
155
+
marked as the latest GitHub release. Users can install those older majors with a
156
+
semver specifier, for example `npm install graphql@16`.
157
+
158
+
Push `<my_release_branch>`, open a PR from `<my_release_branch>` to the target
159
+
release branch, wait for CI to pass, merge the PR, and then approve the GitHub
0 commit comments