Introduced support for publishing to Posit Cloud. This feature is currently in closed beta and requires access to an enabled account on Posit Cloud. See Posit Cloud’s Announcement for more information and to request access.
Update company and product names for rebranding to Posit.
Shiny applications and Shiny documents no longer include an
implicit dependency on ragg
when that package is
present in the local environment. This reverts a change introduced in
0.8.27.
Shiny applications should add an explicit dependency on
ragg
(usually with a library("ragg")
statement) to see it used by shiny::renderPlot
(via
shiny::plotPNG
).
The documentation for shiny::plotPNG
explains the use of
ragg
. (#598)
Fix bug that prevented publishing or writing manifests for
non-Quarto content when a Quarto path was provided to the
quarto
argument of writeManifest()
,
deployApp()
, and related functions.
Escape account names when performing a directory search to determine an appropriate server. (#620)
quarto
argument. (#594).rscignore
. (#599)appDir
and
quarto
binary but not an appPrimaryDoc
work
more consistently. A directory containing a .qmd
file will
deploy as Quarto content instead of failing, and a directory containing
an .Rmd
file will successfully deploy as Quarto content
instead of falling back to R Markdown. (#601)ragg
package is installed locally, it is now
added as an implicit dependency to shiny
apps since
shiny::renderPlot()
now uses it by default (when
available). This way, shiny
apps won’t have to add
library(ragg)
to get consistent (higher-quality) PNG images
when deployed. (#598)openssl
version to 2.0.0 to enable
publishing for users on FIPS-compliant systems without the need for API
keys. (#452)writeManifest
, which requires
passing the absolute path to a Quarto executable to its new
quarto
parameterquarto
parameter to deployApp
to
enable deploying Quarto documents and websites by supplying the path to
a Quarto executablejupyter
runtimeimage
in the
bundle manifestshowLogs
function takes a server
parameter. (#57)rsconnect.tar
option, which can be used to
specify the path to a tar
implementation instead of R’s
internal implementation. The previous method, using the
RSCONNECT_TAR
environment variable, still works, but the
new option will take precedence if both are set.curl
option -T
when uploading
files to avoid out of memory errors with large files. (#544)rsconnect.max.bundle.size
and
rsconnect.max.bundle.files
options are enforced when
processing an enumerated set of files. Previously, these limits were
enforced only when bundling an entire content directory. (#542)tools::R_user_dir
. Configuration created
by earlier versions of this package is automatically migrated to the new
location. (#550).rscignore
file to exclude files or
directories from publishing (#368)R CMD CHECK
R_USER_CONFIG_DIR
shiny.R
instead of server.R
(#509)verbose
option to writeManifest
utility (#468)options(rsconnect.http.trace.json = TRUE)
could cause
deployment errors with some HTTP transports (#490)RSCONNECT_TAR
environment variable can be used to
select the tar implementation used to create bundles (#446)showUsers()
(#398)connectApiUser()
did not set a user id
(#407)deployApp
to force the generation of a
Python environment file or a requirements.txt
file
(#409)server.R
is present (#461)packrat
0.5 or later (#434)writeManifest()
no longer reference
packrat
files in the generated manifest.json
.
The packrat
entries were transient and only existed while
computing dependencies. (#472)applications
when ShinyApps does not return
size
details (#496)browser()
debugging calls when deploying
(#196)appId
and other global deployment parameters to
deploySite
(#231)deployments()
without any
registered accounts (#261)renv
files from deployment bundle (#367)RETICULATE_PYTHON
when writing manifests
(#374)on.failure
user hook to run a function when
deployApp()
fails (#375)requirements.txt
for Python, if it
exists (#386)purgeApp()
function to purge previously deployed
shinyapps.io applications (#352)