codex - 💡(How to fix) Fix Version numbering policy (e.g. reason for missing `0.126.0` and `0.127.0`)? [1 comments, 2 participants]

TL;DR

The release notes of the skipped version's subsequent release should contain all changes since the previous stable version, not just the changes since the immediately preceding version.

Guidance

• To verify if the release notes contain all changes since the previous stable version, check the release notes of the subsequent version for a comprehensive changelog.
• When skipping version numbers, it's essential to ensure that the release notes of the subsequent version accurately reflect all changes made since the previous stable version.
• If the release notes only contain changes since the immediately preceding version, it may be necessary to review the commit history or changelogs of the skipped versions to get a complete understanding of the changes.
• Consider reaching out to the maintainers of codex to confirm their policy on release notes and version skipping.

Notes

The issue lacks information on the specific release notes or version control system used by codex, so it's difficult to provide a more detailed solution.

Recommendation

Apply workaround: Review the commit history or changelogs of skipped versions to ensure a complete understanding of changes, as the release notes of the subsequent version may not always contain all changes since the previous stable version.