Skip to content

Releases: rstudio/rsconnect

rsconnect 1.10.0

Choose a tag to compare

@aronatkins aronatkins released this 08 Jun 20:04
v1.10.0

Increment version number to 1.10.0

rsconnect 1.8.0

Choose a tag to compare

@aronatkins aronatkins released this 10 Apr 16:01
  • rsconnect now uses httr2 as its HTTP client.
    There should be no user-visible changes as a result, but if something does
    not work as expected, please file an issue, and you can set
    options(rsconnect.httr2 = FALSE) as a temporary workaround. (#1284)

  • Added support for renv profiles and renv lockfiles that are located outside of
    the project root. (#1122)

  • Resolved a bug where renv.lock files that had multiple repositories were not
    being translated faithfully when creating the manifest file. (#1268)

  • Packages installed locally via pak are resolved against configured
    repositories. (#1305)

  • Added support for overriding R package repository resolution behavior. (#1272)

  • Push-button publishing from desktop RStudio is now compatible with Connect
    servers hosted on Snowflake. This includes support for browser-based
    authentication during deployment. (#1289)

  • The snowflakeConnectionName parameter now respects the default Snowflake
    connection name in the connections.toml file (when it exists), making it
    optional in many cases. This is only applicable to Connect servers hosted on
    Snowflake. (#1283)

  • Added support for using identity federation to authenticate against Connect
    when running in Posit Workbench, when available. This allows deploying to
    Connect servers without the need to store long-lived credentials. (#1287)

  • Upgraded to use v1 APIs for deploying to Connect servers, which enables
    new features for specifying settings in the manifest file. (#1280)

  • Removed support for log streaming from shinyapps.io due to loss of support
    for this feature on the shinyapps.io platform (showLogs(streaming = TRUE)).
    If this feature is important to your workflow, please file an issue and we
    will consider reintroduction of log streaming via rsconnect in Connect Cloud.
    (#1292)

  • Removed several functions, including addConnectServer() and
    discoverServer(), as well as HTTP backends other than libcurl,
    which were deprecated in rsconnect 1.0.0. (#1282)

rsconnect 1.7.0

Choose a tag to compare

@aronatkins aronatkins released this 08 Dec 14:04
  • Added support for deploying from manifest.json files created by
    writeManifest(): use the manifestPath argument of deployApp() and related
    functions to specify the path to an existing manifest file. (#1259)

  • urlEncode() now uses curl::curl_escape() instead of RCurl::curlEscape(),
    as RCurl is a Suggests dependency. (#1265)

  • The User-Agent header in requests made from rsconnect will now be of the
    format RSConnect/x.y.z instead of rsconnect/x.y.z in order to satisfy web
    application firewalls that enforce Pascal case.

rsconnect 1.6.2

Choose a tag to compare

@aronatkins aronatkins released this 18 Nov 14:22
  • Fix an opaque error when creating a manifest using Python <= 3.10 with a
    version requirement in a pyproject.toml file. A warning is shown rather
    than an error when the tomllib package is not present. (#1226)

  • Address CRAN test failures caused by some openssl configurations. (#1255)

rsconnect 1.6.1

Choose a tag to compare

@aronatkins aronatkins released this 05 Nov 20:24
  • Fix account registration from RStudio. (#1250)

  • SPCS/Snowflake authentication supports Connect API keys for user
    identification. The connectSPCSUser() function now requires an apiKey
    parameter, and the API key is included in the X-RSC-Authorization header
    alongside Snowflake token authentication. This aligns with updated Connect
    server requirements where Snowflake tokens provide proxied authentication
    while API keys identify users to the Connect server itself.

rsconnect 1.6.0

Choose a tag to compare

@aronatkins aronatkins released this 28 Oct 13:02
  • Support deploying to Posit Connect Cloud. Use connectCloudUser() to add
    Connect Cloud credentials.

  • rsconnect now sets the rsconnect.max.bundle.size and
    rsconnect.max.bundle.files options to their default values on startup
    if they have not yet been set. (#1204)

  • The default rsconnect.max.bundle.size limit has increased to 5 GiB. (#1200)

  • getLogs() returns log lines for a shinyapps.io hosted application. (#1209)

  • Python environment inspection errors include the path to the target Python
    binary. (#1207)

  • Improve cookie expiration date handling. (#1212)

  • Improve documentation and advice for deployApp(envVars...).

  • Removed support for publishing to Posit Cloud. (#1215)

    Existing Posit Cloud account records may be removed by using
    removeAccount("yourname", "posit.cloud").

    Existing Posit Cloud deployment records may be removed by using
    forgetDeployment(name="deployment", account="yourname", server="posit.cloud").

  • Removed the Posit Cloud-exclusive space argument from deployApp(). (#1215)

rsconnect 1.5.1

Choose a tag to compare

@aronatkins aronatkins released this 28 Aug 13:54
  • Address user registration for Posit Connect deployments hosted in Snowpark
    Container Services when there is more than one configured Snowflake
    connection. (#1189)

  • Process cookie expiration dates in addition to the cookie max-age. Some
    servers return already-expired cookies. (1187)

  • Removed unused internal methods from Connect client. (#1182)

rsconnect 1.5.0

Choose a tag to compare

@aronatkins aronatkins released this 26 Jun 17:11
  • Functions for interacting with Posit Connect deployments in
    Snowpark Container Services are now provided by the snowflakeauth package.

rsconnect 1.4.2

Choose a tag to compare

@aronatkins aronatkins released this 18 Jun 16:10
  • Address duplicate certificate errors on macOS with newer curl. (#1175)

rsconnect 1.4.1

Choose a tag to compare

@aronatkins aronatkins released this 22 May 12:25
  • Fixed processing error during server validation, which prevented
    registration of new Connect accounts. (#1166)

  • When waiting for initial Connect account authorization, allow HTTP 401
    responses. (#1167)