Repository navigation
--override-python-version 3.11 is pinned as ==3.11.0, which no Connect installation matches #901
Description
🤖 --override-python-version 3.11 (major.minor only) is written as an exact 3.11.0 pin. No Connect server ships x.y.0, so the deploy fails.
Repro
rsconnect write-manifest api --override-python-version 3.11 .
grep -A2 '"python"' manifest.json # "version": "3.11.0"
grep requires manifest.json # "requires": "==3.11.0"Deploying against a server with Python 3.11.15 fails because no installation matches ==3.11.0. Passing 3.11.15 works.
Expected
For a major.minor value, emit ~=3.11.0 (or ==3.11.*) and don't pad the version to .0. Alternatively, reject values without a patch component with a clear error.
Found during live QA of #892 against Posit Connect. Reproduced on 1.32.0 and current main (0287aca3).
Reacted by Alessandro Molina
Activity
tdstein commentedon Oct 28, 2026
🤖 Steering for PR #911: CI fails at the
just lintstep on every job, so the test suite never runs. The code passesruff check. The failure isruff format --check: it would reformattests/test_main.py, specifically theCliRunner().invoke(cli, [...])argument list you added (around line 2170). That list packs several arguments onto each line.To fix:
just fmt(oruv run ruff format tests/test_main.py) and commit the result. Ruff splits the list to one argument per line.just lintanduv run pytest tests/test_main.pylocally before pushing.