Zach Kellingandhanzo-dev
4a713aebc4
Same drift as the CLI, in all three packages: a hardcoded __version__ that no
longer matched pyproject.
hanzo_iam/__init__.py 1.1.1 vs pyproject 1.30.0 (29 minor versions apart)
hanzo_cli/__init__.py 0.1.0 vs pyproject 0.2.2
The hanzo_cli one was load-bearing: click's version_option reads it, so it is
the reason `hanzo --version` answered "0.1.0" — a release that never existed.
All three now resolve from the installed distribution, so there is one answer.
Patch bumps for the two packages changed in 205f1c03 (never a lazy major):
hanzo-cli 0.2.2 -> 0.2.3 entry point removed, __main__ added, PKCE, token path
hanzo-iam 1.30.0 -> 1.30.1 endpoint properties on the exported IAMConfig
Verified on a clean venv: __version__ == importlib.metadata.version for all
three, `hanzo --version` 0.4.4, `python -m hanzo_cli --version` 0.2.3, 58
commands. hanzo-iam 19/19; hanzo-cli's failures are unchanged live-service auth.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
12 lines
507 B
Python
12 lines
507 B
Python
"""Hanzo CLI — unified command-line interface for the Hanzo platform."""
|
|
|
|
from importlib.metadata import PackageNotFoundError, version as _version
|
|
|
|
try:
|
|
# Single-sourced from the installed distribution. This said "0.1.0" while
|
|
# pyproject said 0.2.2, and click's version_option read THIS — which is why
|
|
# `hanzo --version` reported a release that never existed.
|
|
__version__ = _version("hanzo-cli")
|
|
except PackageNotFoundError: # source tree, not installed
|
|
__version__ = "0.0.0+dev"
|