Tags v0.26.4 and v0.26.5 both declare version 0.26.4 — intended?

[luizfnsilva]

Hi, a question about release history, not a bug report.

I maintain a tool that checks whether a version label names one state of the code (closure_drift). On this repository it reports that the tags v0.26.4 and v0.26.5 both declare version 0.26.4 in openai/version.py, while four files under openai/ differ between them.

To reproduce:

pip install https://github.com/luizfnsilva/closure_drift/releases/download/v0.9.1/closure_drift-0.9.1-py3-none-any.whl
closure-drift --compare v0.26.4 v0.26.5
This is old history (early 2023) and I am not suggesting anything needs fixing. I would like to know whether the tag was simply created before the version bump, so I can classify the case correctly. Method and all cases: https://github.com/luizfnsilva/closure_drift/blob/main/tools/study/STUDY.md

Thank you.

[NotAFlightRisk]

The v0.26.5 tag points one commit before the bump. It's on 5386db1 (the #216 commit), where openai/version.py still says 0.26.4. The next commit on main is cf8a275, "Bump version to 0.26.5 (#217)", merged six minutes later and changing nothing but that line.

The 0.26.5 sdist on PyPI says VERSION = "0.26.5" and its source matches cf8a275 (bar setuptools rewriting setup.cfg), so the published 0.26.5 is the post-bump commit, not the tagged tree. It's a lightweight tag though, so git can't tell you when the tag itself was made, only where it points.

It's not a one-off either. v0.27.6 and v0.27.10 also tag a commit whose version.py is one release behind - the v0.27.6 bump is the next commit and got its own v0.27.6v2 tag, and the v0.27.10 bump never left a side branch.

[luizfnsilva]

Thank you, that is exactly the detail I was missing, and it matches what the tool lists for this repository (v0.26.5, v0.27.6, v0.27.10). I've recorded it, with a link to this thread, in the study's later reading.

[NotAFlightRisk]

No worries, happy to help :)