Two months after the last release, here is Nim 2.0.6, and it is a huge one: https://nim-lang.org/blog/2024/06/17/version-206-released.html
We recommend everyone to upgrade to it.
Can you expand on:
NOTE: If your program uses threads (--threads:on became the default in the 2.0.x line) please also use the -d:useMalloc switch. This problem will be fixed in a future release, sorry for the inconvenience.
What is this issue here? Does this affect 2.0.2, 2.0.4, or just 2.0.6?
Side note: what is with the increment by 2 each version release on https://nim-lang.org/install.html ?
The reason for this many commits in this release is that this is planned as the last 2.0.x release before Nim 2.2
No 2.1.x branch?
const
NimMajor* {.intdefine.}: int = 2
## is the major number of Nim's version. Example:
## ```
## when (NimMajor, NimMinor, NimPatch) >= (1, 3, 1): discard
## ```
# see also std/private/since
NimMinor* {.intdefine.}: int = 0
## is the minor number of Nim's version.
## Odd for devel, even for releases.
NimPatch* {.intdefine.}: int = 4
## is the patch number of Nim's version.
## Odd for devel, even for releases.Does this affect 2.0.2, 2.0.4, or just 2.0.6?
Yes, it is also present in Nim 2.0.4 and 2.0.2, see the 2.0.4 announcement, for example. So no new regressions there.
why does each release announced on the install page increment by 2?
Because that way it is easy for us (and tools) to disambiguate between development versions (odd) and the official releases (even).
No 2.1.x branch?
If you want to use Nim 2.1.x, you can use current Nim devel ;)