rsconnect-python v1.31.1

[samperman]

Routine version bump from 1.31.0 to 1.31.1.

Upstream 1.31.1 is a single fix: deploys to Posit Connect Cloud now request the Python version the content needs, instead of leaving Connect Cloud to fall back to Python 3.9.

No recipe changes beyond the version and hash. Between the 1.31.0 and 1.31.1 tags, pyproject.toml differs only in the version string — the run dependencies and the uv_build>=0.9.0,<0.13.0 backend range are unchanged.

The sha256 was verified by downloading rsconnect_python-1.31.1.tar.gz from the URL in the recipe and hashing it.

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (not needed for a version and hash bump; last rerender was 2026-04-29 with conda-smithy 3.61.2 and builds are green)
• Ensured the license file is being packaged (LICENSE.md is present in the sdist)

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

• ℹ️ top-level output overrides versions pinned in the feedstock:
  ['- In section host: python 9999']
  Requirement spec should not list version specifiers to respect conda-forge-pinning. If you need to force another version, please override the pin via conda_build_config.yaml.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/34480314847. Examine the logs at this URL for more detail.}