Tag 0.14.1 declares version 0.14.0 — intended?

[luizfnsilva]

Hi, a small 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 httpcore it reports that the tags 0.14.0 and 0.14.1 both have version = "0.14.0" in httpcore/init.py, while seven files under httpcore/ differ between them.

To reproduce:

pip install https://github.com/luizfnsilva/closure_drift/releases/download/v0.9.0/closure_drift-0.9.0-py3-none-any.whl
closure-drift --compare 0.14.0 0.14.1
Was the version bumped after the tag was created, or is there a release convention I am misreading? Either answer helps me classify the case correctly. The method and every case I looked at are public: https://github.com/luizfnsilva/closure_drift/blob/main/tools/study/STUDY.md

Thanks for your time.

[xop01]

The tag and the version string disagree. That is a missed bump, not a release rule.

0.14.0 is the commit "Version 0.14" from 2021-11-11. 0.14.1 is the next day's commit, "max_connections should be optional (#429)". On that commit httpcore/__init__.py still has __version__ = "0.14.0". setup.py takes the version from that line, so a build of the 0.14.1 tag still calls itself 0.14.0. The tree is 4 commits ahead of 0.14.0.

The next tag, 0.14.2, does set __version__ to "0.14.2". Classify 0.14.1 as a tag that moved the code and left the version string behind.

@luizfnsilva

[luizfnsilva]

Thank you, that settles it. I've recorded 0.14.1 as a missed bump, with a link to this thread, in the study's later reading: https://github.com/luizfnsilva/closure_drift/blob/main/tools/study/posthoc.md