From 3ead5039e6bd2ba43d4ae1f7203e0ace92478530 Mon Sep 17 00:00:00 2001 From: Andrew Cherniavskii Date: Mon, 30 Dec 2024 17:10:14 +0100 Subject: [PATCH] [core] Update the `release:version` docs (#16038) --- scripts/README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/scripts/README.md b/scripts/README.md index 1df7b04885a3e..fb4a7bfb4f554 100644 --- a/scripts/README.md +++ b/scripts/README.md @@ -55,6 +55,10 @@ In case of a problem, another method to generate the changelog is available at t 3. `pnpm release:publish` (release the versions on npm, you need your 2FA device) 4. `pnpm release:tag` (push the newly created tag) +> [!WARNING] +> If the `pnpm release:tag` fails you can create and push the tag using the following command: `git tag -a v4.0.0-alpha.30 -m "Version 4.0.0-alpha.30" && git push upstream --tag`. +> Make sure to copy the git tag command above so that the tag is annotated! + ### Publish the documentation The documentation must be updated on the `docs-vX` branch (`docs-v4` for `v4.X` releases, `docs-v5` for `v5.X` releases, ...) @@ -100,10 +104,6 @@ You can use the following script in your browser console on any GitHub page to a })(); ``` -### Manually create the release tag - -If the `pnpm release:tag` fails you can create and push the tag using the following command: `git tag -a v4.0.0-alpha.30 -m "Version 4.0.0-alpha.30" && git push upstream --tag`. - ### release:publish failed If you receive an error message like `There are no new packages that should be published`. Ensure you are publishing to the correct registry, not `verdaccio` or anything else. If you need to reset your configuration, you can run `npm config delete registry`.