PyPi version is out of date

[danielbrunt57]

@alandtse,

GitHub has a v1.3.6 release/tag, but PyPI still shows 1.3.3 (so alexapy Poetry fails resolving authcaptureproxy ^1.3.6).

Is 1.3.6 still being tested or can it be published & released via alexapy?

Is there an existing PyPI publish workflow (GitHub Actions / trusted publishing) that should run on tags, or is publishing done manually (e.g., poetry publish)?

Happy to pin alexapy to the git tag temporarily if publishing to PyPI isn’t intended.

[danielbrunt57]

Hi @alandtse,
I installed from the v1.3.6 tag via pip (git URL) and pip built authcaptureproxy-1.3.3-...whl and pip show reports version 1.3.3. Looks like the project version in pyproject.toml wasn’t bumped to 1.3.6 before tagging/releasing, so packaging tools still treat it as 1.3.3.

[danielbrunt57]

The v1.3.6 tag still has version = "1.3.3" in pyproject.toml, so pip builds it as 1.3.3. That explains why PyPI and Poetry can’t see 1.3.6. It looks like the project version wasn’t bumped before tagging.

[alandtse]

There's an issue to fix it #43