Skip to content

Commit

Permalink
docs(nx): Version error in documentation page (#29440)
Browse files Browse the repository at this point in the history
Original text was:

e.g. `nx@19.2.0` and `@nx/js@20.2.0` should be used together.

Surely it should be...

e.g. `nx@19.2.0` and `@nx/js@19.2.0` should be used together.
  • Loading branch information
jimmcslim authored Dec 20, 2024
1 parent 8516634 commit 6e41b30
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/shared/reference/releases.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@
This page covers the releases of the Nx tooling itself. If you are looking for guidance on releasing your project with Nx Release, [see the documentation on managing releases](/features/manage-releases).
{% /callout %}

The `nx` package, and all packages under the `@nx` namespace which live alongside each other in the [https://github.com/nrwl/nx](https://github.com/nrwl/nx) repository, are released together in lockstep. You should always use matching versions of the `nx` package and the `@nx` packages, e.g. `nx@19.2.0` and `@nx/js@20.2.0` should be used together.
The `nx` package, and all packages under the `@nx` namespace which live alongside each other in the [https://github.com/nrwl/nx](https://github.com/nrwl/nx) repository, are released together in lockstep. You should always use matching versions of the `nx` package and the `@nx` packages, e.g. `nx@19.2.0` and `@nx/js@19.2.0` should be used together.

Major Nx versions are released as the _latest_ every six months, typically around April and October.
After each major version release, the _previous_ major version moves to long-term support (LTS) for 12 months, after
Expand Down

0 comments on commit 6e41b30

Please sign in to comment.