nm-version.h: use the right value of NM_API_VERSION

After the changes in release.sh in previous commits, during development
the value of NM_VERSION will always be the next version, not the latest
released one. As a consequence, we don't need to set MICRO+1 in
NM_API_VERSION, which was a temporary workaround.

(cherry picked from commit 36275bc51c)
This commit is contained in:
Íñigo Huguet 2025-12-23 16:05:03 +01:00
parent 045f328512
commit 8f3b8e0200

View file

@ -82,15 +82,15 @@
/* For releases, NM_API_VERSION is equal to NM_VERSION.
*
* For development builds, NM_API_VERSION is the next
* stable API after NM_VERSION. When you run a development
* For development and RC builds, NM_API_VERSION is the next
* stable API after NM_VERSION. When you run a devel or RC
* version, you are already using the future API, even if
* it is not yet released. Hence, the currently used API
* version is the future one. */
#define NM_API_VERSION \
(((NM_MINOR_VERSION % 2) == 1) \
? NM_ENCODE_VERSION(NM_MAJOR_VERSION, NM_MINOR_VERSION + 1, 0) \
: NM_ENCODE_VERSION(NM_MAJOR_VERSION, NM_MINOR_VERSION, NM_MICRO_VERSION + 1))
: NM_VERSION)
/* deprecated. */
#define NM_VERSION_CUR_STABLE NM_API_VERSION