Upgrade and the green branch

If a catalog entry uses a branch revision (main, master, develop), that ref is the channel. You do not cut a tag just so another developer can consume a merge.

lpip install libfoo
# … a PR merges to the branch the catalog tracks …
lpip upgrade libfoo
# or: lpip install --upgrade libfoo

upgrade / install --upgrade pass pip --upgrade. Pip will not always refetch the same git+ URL without that flag.

This only works if the default branch stays green. CI on that branch is the release gate for day-to-day sharing.

Use lpip install name==1.2.3 (Git tags that parse as PEP 440) when you need a pin you can roll back to. Tags are the product channel. Branch tips are the integration channel.

To install a specific commit (or any other Git ref) without changing the catalog or cutting a tag:

lpip install libfoo --revision abc1234
lpip upgrade libfoo --revision abc1234

Short and full SHAs are both valid if Git can resolve them. --revision does not combine with == or with -r.

For a CLI on PATH (no project venv), use pipx via the same catalog:

lpipx install mycli
lpipx upgrade mycli
# or: lpip install mycli --pipx

That runs pipx install --force with the rendered Git URL. It does not call pipx upgrade. --pipx / lpipx does not combine with -r.

lpip versions libfoo lists those tags.