You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Release 1.34.0 following CONTRIBUTING.md, then open an issue on posit-dev/posit-cli suggesting it raise its requires-python floor to match. That issue does not block the release.
Acceptance criteria
1.34.0 is published to PyPI and requires Python >=3.11
Installing on Python 3.8 resolves to 1.33.2 (carried over from Release 1.33.2 #947)
The feedstock recipe doesn't read requires-python. Its runtime floor is conda-forge's global python_min: python >={{ python_min }}. If 1.34.0 is bumped only for version, URL and checksum, as CONTRIBUTING.md describes, conda users on Python 3.10 get a CLI that crashes on import (tomllib, typing.NotRequired).
In the 1.34.0 feedstock PR:
Add {% set python_min = "3.11" %} at the top of recipe/meta.yaml, so the host, run and test Python pins all move to 3.11.
Activity
tdstein commentedon Nov 12, 2026
conda-forge recipe needs more than a version bump
The feedstock recipe doesn't read
requires-python. Its runtime floor is conda-forge's globalpython_min:python >={{ python_min }}. If 1.34.0 is bumped only for version, URL and checksum, asCONTRIBUTING.mddescribes, conda users on Python 3.10 get a CLI that crashes on import (tomllib,typing.NotRequired).In the 1.34.0 feedstock PR:
{% set python_min = "3.11" %}at the top ofrecipe/meta.yaml, so thehost,runandtestPython pins all move to 3.11.typing_extensions >=4.8.0fromrequirements.run. feat!: require Python 3.11 for the CLI #972 dropped it as a runtime dependency.run:pins against[project].dependenciesinpyproject.toml.CONTRIBUTING.mdto say: whenrequires-pythonor the dependencies change, updatepython_minand therun:list too.