From fea232ee32b7011da8499aa3787b4da036a6345f Mon Sep 17 00:00:00 2001 From: Nicolas Belliard Date: Fri, 7 Jun 2024 14:26:25 +0200 Subject: [PATCH] docs(core): upgade major version in contributing doc (#26442) Hello! Little fix of the contributing doc that I faced during the install of nx in my local environment. ## Current Behavior The major version used in the contributing is the 18.0.0 ## Expected Behavior It should be the 20.0.0 --- CONTRIBUTING.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 487abd6e61..1919755b30 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -76,13 +76,13 @@ Check out [this video for a live walkthrough](https://youtu.be/Tx257WpNsxc) or f - Run `pnpm local-registry` in Terminal 1 (keep it running) - Run `npm adduser --registry http://localhost:4873` in Terminal 2 (real credentials are not required, you just need to be logged in. You can use test/test/test@test.io.) -- Run `pnpm nx-release 18.0.0 --local` in Terminal 2 - you can choose any nonexistent version number here, but it's recommended to use the next major +- Run `pnpm nx-release 20.0.0 --local` in Terminal 2 - you can choose any nonexistent version number here, but it's recommended to use the next major - Run `cd ./tmp` in Terminal 2 -- Run `npx create-nx-workspace@18.0.0` in Terminal 2 +- Run `npx create-nx-workspace@20.0.0` in Terminal 2 If you have problems publishing, make sure you use Node 18 and NPM 8. -**NOTE:** To use this newly published local version, you need to make a new workspace, run `nx migrate` or change all of your target packages to this new version, eg: `"nx": "^18.0.0",` and re-run `pnpm i` in your testing project. +**NOTE:** To use this newly published local version, you need to make a new workspace, run `nx migrate` or change all of your target packages to this new version, eg: `"nx": "^20.0.0",` and re-run `pnpm i` in your testing project. ### Publishing for Yarn 2+ (Berry)