[tdstein]

Summary

newer PyPI release
  compatible or unknown Python requirement → existing pip upgrade hint
  incompatible Python requirement → Python version notice and uv install command

Cache the release's Python requirement and refresh legacy cache entries. The uv command selects a compatible Python and adds --force when the current installation has no uv receipt.

Evidence

• Before: an incompatible newer release received the pip upgrade hint.
• After: deploy CLI tests cover compatible, incompatible, legacy-cache, and disabled checks, including both uv receipt states.
• Python 3.14 deploy and CLI tests: 192 passed, 12 skipped; Python 3.8 version-check tests: 18 passed; Ruff checks passed.

Merge Danger

Door: Two-way

Blast Radius: Deploy notices

Closes #945

[github-actions]

PR Preview Action v1.8.2
🚀 View preview at https://posit-dev.github.io/rsconnect-python/pr-preview/pr-953/
Built to branch gh-pages at 2026-11-10 16:55 UTC. Preview will be ready when the GitHub Pages deployment is complete.

[github-actions]

☂️ Python Coverage

current status: ✅

Overall Coverage

Lines	Covered	Coverage	Threshold	Status
11208	9990	89%	0%	🟢

New Files

No new covered files...

Modified Files

File	Coverage	Status
rsconnect/version_check.py	93%	🟢
TOTAL	93%	🟢

updated for commit: b421dee by action🐍

[tdstein]

🤖 I ran the version check by hand on Python 3.8, 3.13, 3.15 and 3.16.0a1, using a wheel stamped 1.0.0, real deploy runs and an isolated HOME. Detection works in every case: the incompatible notice, upper bounds, prerelease interpreters, old-format caches, invalid specifiers, RSCONNECT_DISABLE_VERSION_CHECK, --quiet and non-deploy commands.

The suggested command is the one problem; details inline. Users who see this notice are, by definition, running a Python the latest release doesn't support, so a bare uv tool install rsconnect-python usually lands them on an older release.