Skip to content

rsconnect-python v1.31.0 - #56

Merged
edavidaja merged 1 commit into
conda-forge:mainfrom
samperman:update-1.31.0
Sep 8, 2026
Merged

rsconnect-python v1.31.0#56
edavidaja merged 1 commit into
conda-forge:mainfrom
samperman:update-1.31.0

Conversation

@samperman

Copy link
Copy Markdown
Contributor

Updates the recipe from 1.29.0 to 1.31.0, and fixes the build so it works with the new upstream build backend.

The recipe has been stuck on 1.29.0. rsconnect-python switched its build backend from setuptools + setuptools_scm to uv_build in 1.30.0 (posit-dev/rsconnect-python#808), which is why the autotick bot's 1.30.0 PR (#55) fails with:

pip._vendor.pyproject_hooks._impl.BackendUnavailable: Cannot import 'uv_build'

The bot only bumps the version and hash, so it can't repair this on its own. This PR goes straight to 1.31.0; #55 can be closed as superseded once this merges.

Changes

  • Build with uv-build instead of setuptools_scm. The version is a static field in pyproject.toml now, so SETUPTOOLS_SCM_PRETEND_VERSION no longer does anything and is dropped. --no-build-isolation is added so pip resolves the backend from the host environment rather than trying to reach PyPI.
  • Source from the PyPI sdist rather than the GitHub tag archive. It is the artifact upstream publishes and tests, and it contains LICENSE.md.
  • Run dependencies synced with pyproject.toml: dropped six; added typing_extensions, uv, packaging and toml; widened semver to <4.0.0. Upstream declares toml only for python_version < "3.11", but selectors are not allowed in a noarch: python recipe, so it is listed unconditionally — it is pure Python and simply unused on 3.11+.
  • Homepage points at posit-dev, where the repository lives now. The old rstudio URL only resolves through a GitHub redirect.
  • Smoke-test the entry point with rsconnect version, which is offline-safe.
  • Added samperman as a recipe maintainer (myself; I work on rsconnect-python upstream).

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 (requesting below — the CI scaffolding is stale)
  • Ensured the license file is being packaged

The recipe has been stuck on 1.29.0. Since then rsconnect-python switched
its build backend from setuptools + setuptools_scm to uv_build (in 1.30.0),
which is why the autotick bot PR for 1.30.0 fails with
"BackendUnavailable: Cannot import 'uv_build'".

- Build with uv-build instead of setuptools_scm. The version is now a
  static field in pyproject.toml, so SETUPTOOLS_SCM_PRETEND_VERSION is
  no longer needed. --no-build-isolation lets pip use the host uv-build.
- Take the source from the PyPI sdist rather than the GitHub tag archive.
- Sync run dependencies with pyproject.toml: drop six, add
  typing_extensions, uv, packaging and toml, and widen semver to <4.0.0.
- Point the homepage at posit-dev, which is where the repo lives now.
- Smoke-test the rsconnect entry point.
- Add samperman as a recipe maintainer.
@samperman

Copy link
Copy Markdown
Contributor Author

@conda-forge-admin, please rerender

@conda-forge-webservices

Copy link
Copy Markdown
Contributor

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you but ran into an issue with kicking GitHub Actions to do the rerender.
Please ping conda-forge/core for further assistance. You can also try re-rendering locally.

@edavidaja
edavidaja merged commit 9860b13 into conda-forge:main Sep 8, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants