Version numbering policy (e.g. reason for missing `0.126.0` and `0.127.0`)?

Resolved 💬 1 comment Opened May 2, 2026 by your-diary Closed May 2, 2026

I regularly check the release notes of codex, and often find some versions are skipped when a stable release is published.

For example, the next stable version after 0.125.0 is 0.128.0; 0.126.0 and 0.127.0 were skipped.

Regarding this, I have two questions:

  • Just out of curiosity, why do you sometimes skip some version numbers? This is a bit inconvenient because I usually compare the latest version number with the local one to estimate how far behind I am.
  • More importantly, when you release the version $N + M$ after the version $N$, skipping $N + 1,\ N + 2,\ \cdots,\ N + M - 1$, can we expect that the release note of the version $N+M$ contains all changes since the version $N$, not just the changes since $N + M - 1$?

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗