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
{{ message }}
Repository navigation
Version check: notice when the latest release excludes the running Python #945
On deploy commands, the upgrade check learns whether the latest rsconnect-python release on PyPI can run on the user's CLI Python. If the latest version is newer but its requires_python excludes the running interpreter, users see a notice instead of the "upgrade available" hint. The notice names the latest version, its requires_python, the running Python version, and suggests uv tool install rsconnect-python. Users on compatible interpreters see the existing hint unchanged.
The PyPI response already carries info.requires_python, so no new requests are needed. The on-disk cache stores requires_python next to the latest version. A cache entry written by an earlier release (without requires_python) is treated as stale and refreshed, and is treated as compatible until then. A missing or unparseable requires_python counts as compatible. Existing gating is unchanged: deploy commands only, stderr, RSCONNECT_DISABLE_VERSION_CHECK, dev versions skipped, 24-hour TTL, background refresh, and a short blocking wait on a cold cache.
Acceptance criteria
When the latest release excludes the running interpreter, deploy commands print the notice on stderr and not the pip install --upgrade hint
When the latest release supports the running interpreter, the existing upgrade hint is unchanged
A cache without requires_python doesn't crash and triggers a refresh
RSCONNECT_DISABLE_VERSION_CHECK suppresses both messages
Tests invoke a deploy command through CliRunner, use a temporary config directory, and fake PyPI with httpretty rather than patching version-check internals
CHANGELOG has a "Fixed" entry under the unreleased 1.33.2
Activity