posit-dev/publisher

Add schema support for newer Connect Python, Quarto, and R version matching specifiers

Open

#2,661 opened on Jun 4, 2025

View on GitHubContributor guide
 (3 comments) (0 reactions) (0 assignees)TypeScript (6 forks)auto 404
enhancementgood first issue

Repository metrics

Stars
 (14 stars)
PR merge metrics
 (PR metrics pending)

Description

Description

Connect now supports version matching specifiers in the manifest.json However, Publisher does not appear to utilize data from an existing manifest.json if present. There does not appear to be a documented way to present this specific data in the existing Publisher deployment configuration.

This was discovered while attempting deployment of connect-extensions which have been heavily utilizing these new version specifiers.

Posit Connect 2025.05.0

  • Publishers can set version specifiers for Quarto in the manifest.json under environment.quarto.requires (e.g., “>=1.2.0, <2.0.0”). If this field is set, it takes precedence over the Quarto.VersionMatching configuration setting (i.e., nearest, major-minor, and exact). (https://github.com/posit-dev/connect/issues/31234)

Posit Connect 2025.03.0

  • Publishers can set version specifiers (e.g., “>=3.8, <4”) for both R and Python in the manifest.json under environment.r.requires and environment.python.requires, respectively. If these fields are set, they take precedence over the Connect version matching strategies (i.e., nearest, major-minor, and exact). (https://github.com/posit-dev/connect/issues/30062, #30063)

Contributor guide

Research direction
Investigate how Connect's manifest.json handles version specifiers for R, Python, and Quarto. Look at the relevant Connect release notes and internal ticket links. Then determine where in Publisher's schema (likely in deployment configuration) these specifiers should be added. Consider adding fields like env.r.requires, env.python.requires, env.quarto.requires to the configuration.
Tech stack
typescriptpythonr
Domain
backenddevops
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitNode.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60