rsconnect-python v1.31.0 - #56
Merged
Merged
Conversation
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
requested review from
amol-,
aronatkins,
dbkegley,
edavidaja and
tdstein
as code owners
September 8, 2026 20:32
Contributor
Author
|
@conda-forge-admin, please rerender |
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. |
edavidaja
approved these changes
Sep 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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_buildin 1.30.0 (posit-dev/rsconnect-python#808), which is why the autotick bot's 1.30.0 PR (#55) fails with: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
uv-buildinstead ofsetuptools_scm. The version is a static field inpyproject.tomlnow, soSETUPTOOLS_SCM_PRETEND_VERSIONno longer does anything and is dropped.--no-build-isolationis added so pip resolves the backend from the host environment rather than trying to reach PyPI.LICENSE.md.pyproject.toml: droppedsix; addedtyping_extensions,uv,packagingandtoml; widenedsemverto<4.0.0. Upstream declarestomlonly forpython_version < "3.11", but selectors are not allowed in anoarch: pythonrecipe, so it is listed unconditionally — it is pure Python and simply unused on 3.11+.posit-dev, where the repository lives now. The oldrstudioURL only resolves through a GitHub redirect.rsconnect version, which is offline-safe.sampermanas a recipe maintainer (myself; I work on rsconnect-python upstream).Checklist
0(if the version changed)