fix(deps): bump typer to >=0.20.0 so the CLI works with click >=8.3 (#650)

[Anai-Guo]

Problem

Running the CLI (infinity_emb v2 ...) crashes at startup when click >= 8.2/8.3 is installed:

TypeError: Secondary flag is not valid for non-boolean flag.

(Reported in #650; #649 users hit it after pip install infinity[all] pulls a recent click.)

Root cause

Several CLI options in libs/infinity_emb/infinity_emb/cli.py are declared as list[bool], e.g.:

trust_remote_code: list[bool] = typer.Option(...)
model_warmup:      list[bool] = typer.Option(...)
compile:           list[bool] = typer.Option(...)
onnx_disable_optimize: list[bool] = typer.Option(...)
# ... and more

typer 0.12.x auto-generates a secondary --no-<flag> for each bool, but for a multiple (list[...]) option click 8.2+ now rejects a secondary flag, raising the error above. typer's click-param generation was fixed in later releases — as confirmed in #650, bumping typer makes the error disappear (typer 0.12.5 + click 8.3.0 crashes; recent typer does not).

Fix

The ^0.12.5 constraint pinned typer to the broken 0.12.x line. This bumps the lower bound to >=0.20.0 (the version confirmed working in #650 by @wirthual); poetry lock --no-update resolves typer 0.23.2, which emits click-8.3-compatible params. The poetry.lock change is minimal — only the typer entry, its new transitive dep annotated-doc, and the content hash.

poetry check --lock passes.

If you've verified an even lower typer release works, feel free to relax the bound — I used >=0.20.0 because that's the value explicitly confirmed in the thread.

Closes #650

🤖 Generated with Claude Code

[gemini-code-assist]

Code Review

This pull request updates the typer dependency constraint in pyproject.toml from ^0.12.5 to >=0.20.0. Consequently, the poetry.lock file has been updated, upgrading typer to version 0.23.2 and adding the annotated-doc package as a dependency. No review comments were provided, so there is no additional feedback.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[greptile-apps]

Greptile Summary

This PR bumps the typer lower-bound from ^0.12.5 to >=0.20.0 to resolve a startup crash (TypeError: Secondary flag is not valid for non-boolean flag) that occurs when click >= 8.2/8.3 is paired with typer 0.12.x. The lock file is regenerated with poetry lock --no-update, resolving to typer 0.23.2 and pulling in one new transitive dependency (annotated-doc).

• pyproject.toml: removes the caret (^) upper-bound pin and raises the minimum to >=0.20.0, the first confirmed-working release per the linked issue thread.
• poetry.lock: updates the typer entry from 0.12.5 → 0.23.2, adds the annotated-doc >= 0.0.2 transitive dependency, and refreshes the content hash.

Confidence Score: 4/5

Safe to merge — the dependency bump directly fixes a known startup crash on click >= 8.2/8.3 with no changes to application logic.

The change is a targeted fix for a well-understood compatibility breakage. The only concerns are the missing upper-bound on the typer version range and the unexpected python_version < 3.10 marker on click in the typer 0.23.2 lock entry. Neither issue affects correctness at merge time.

No files require special attention beyond verifying that the production extras (server, all) continue to supply click independently of any dev-group transitive path on Python 3.10+.

Important Files Changed

Filename	Overview
libs/infinity_emb/pyproject.toml	Relaxes typer constraint from ^0.12.5 to >=0.20.0; the fix is correct but leaves no upper-bound ceiling for future major releases.
libs/infinity_emb/poetry.lock	Lock updated to typer 0.23.2; adds annotated-doc 0.0.4 transitive dep; click dependency on the typer entry carries a python_version < 3.10 marker that warrants a second look.

_{Reviews (1): Last reviewed commit: "fix(deps): bump typer to >=0.20.0 so the..." | Re-trigger Greptile}

[greptile-apps]

The new constraint has no upper bound. While removing the caret was necessary to escape the broken 0.12.x line, an uncapped >=0.20.0 means any future major version of typer (e.g., a hypothetical 1.0 with breaking API changes) will satisfy the constraint. A loose upper cap like <2 preserves flexibility for all 0.x releases while guarding against unvetted major-version upgrades.

Suggested change

	typer = {version = ">=0.20.0", optional=true}
	typer = {version = ">=0.20.0,<2", optional=true}

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[greptile-apps]

Click declared Python-version-conditional by typer 0.23.2

The resolved typer 0.23.2 entry declares click only for python_version < "3.10". Typer is fundamentally built on click for all Python versions, so this marker looks like a metadata quirk in that specific release. In this lock file click 8.1.7 ends up as optional = false (pulled in via another path, likely jinja2-cli in the test group), so the runtime dependency chain stays intact today. However, if the non-optional click path is ever removed, users on Python 3.10+ would be missing click at import time and the CLI would crash. Worth verifying that the production extras (server, all) reliably pull in click independent of the test group.