rsconnect 1.3.3

• Avoid "legacy" time zone names in tests, as they are not available by
  default in all environments. Addresses CRAN test failures. (#1115)

rsconnect 1.3.2

• Primary Quarto document detection only considers .R, .Rmd, and .qmd as
  end-of-file extensions. Previously, a file with .R elsewhere in its name,
  such as .Rprofile, was incorrectly considered. (#1106)

• Use the repository name identified by renv when available.packages() does
  not enumerate the package, which occurs for archived packages. (#1110)

• Remove remaining directory layout validation check. (#1102)

• Use the public Connect server API endpoint /v1/tasks/{id} to poll task
  progress. (#1088)

rsconnect 1.3.1

• Skip tests when packages "foreign" and "MASS" are not available. (#1081)

rsconnect 1.3.0

• deployApp(logLevel = "quiet") suppresses Posit Connect deployment task
  output. (#1051)

• deployApp(logLevel = "quiet") and writeManifest(quiet=TRUE) suppress
  output when using renv to analyze dependencies. (#1051)

• deployApp() and writeManifest() receive the default value for the
  image argument from the RSCONNECT_IMAGE environment variable. (#1063)

• deployTF() can deploy a TensorFlow model to Posit Connect. Requires Posit
  Connect 2024.05.0 or higher.

• Skip tests when suggested packages are not available. Skip Quarto tests when
  run by CRAN. (#1074)

rsconnect 1.2.2

• Use internally computed SHA1 sums and PKI signing when SHA1 is disabled
  in FIPS mode. (#768, #1054)

• Allow Quarto content with a rendered script as its primary target. (#1055)

rsconnect 1.2.1

• Restore the LC_TIME locale after computing an RFC-2616 date. (#1035)
• Address a problem inspecting Quarto content when the file names and paths
  needed to be quoted. The resulting manifest lacked information about the
  Quarto runtime, which caused difficult-to-understand deployment errors.
  (#1037)
• Produce an error when Quarto content cannot be inspected. (#1032)

rsconnect 1.2.0

• Addressed a number of republishing and collaboration issues where the
  content was incorrectly published to a new location rather than reusing an
  existing deployment. (#981, #1007, #1013, #1019)

• showLogs(), configureApp(), setProperty(), and unsetProperty()
  search for the application by name when there are no matching deployment
  records. (#985, #989)

• rpubsUpload() correctly records the initial RPubs destination, allowing
  republishing. (#976)

• deployApp() and friends record multi-value metadata entries as
  comma-separated values. (#1017)

• accountInfo() includes name and username fields. Older versions of
  rsconnect store account records with a username field. Recent rsconnect
  versions record name. Both name and username should contain the same
  value. (#1024)

rsconnect 1.1.1

• Added space parameter to deploy directly to a space in Posit Cloud.

• Improve reporting of errors returned by shinyapps.io. (#997)

• Remove most directory layout validation checks. (#998)

• Do not use getOption("available_packages_filters") option when calling
  available.packages(). (#1002)

• Packages installed from source within an renv project are not associated
  with repositories. (#1004)

rsconnect 1.1.0

• Fixed analysis of directories that were smaller than the
  rsconnect.max.bundle.files=10000 limit but larger than the
  renv.config.dependencies.limit=1000 limit. (#968)

• Ignore .env, .venv, and venv files only when they reference Python
  virtual environments. (#972)

• deployApp() and writeManifest() accept optional envManagement,
  envManagementR, and envManagementPy arguments. These args specify whether
  Posit Connect should install packages in the package cache.
  If envManagement is FALSE then Connect will not perform any package
  installation and it is the administrator's responsibility to ensure the
  required R/Python packages are available in the runtime environment. This is
  especially useful if off-host execution is enabled, when the execution
  environment (specified by the image argument) already contains the required
  packages. These values are ignored when
  Applications.ManifestEnvironmentManagementSelection = false.
  Requires Posit Connect >=2023.07.0. (#977)

• Fix account discovery by showProperties(). (#980)

rsconnect 1.0.2

• Fixed redeployments to shinyapps.io where appName is provided, but no local
  record of the deployment exists. (#932)

• deployApp() and writeManifest() now error if your library and renv.lock
  are out-of-sync. Previously it always used what was defined in the renv.lock
  but that was (a) slow and (b) could lead to different results than what you
  see when running locally (#930).

• Deploying from an renv project includes the renv.lock in the bundle. A
  manifest created for an renv project references the renv.lock in the
  manifest.json. (#926)

• Use the environment variable RSCONNECT_PACKRAT to analyze dependencies
  using packrat, as was done prior to rsconnect-1.0.0. Use of the
  rsconnect.packrat option is discouraged, as it is not effective when using
  push-button deployment in the RStudio IDE. (#935)

• The renv.lock is ignored when the RSCONNECT_PACKRAT environment variable
  or the rsconnect.packrat option is set. (#936)

• The content type is inferred by analyzing the set of top-level files. (#942)

• deployApp() and writeManifest() accept an optional appMode argument.
  Provide this argument if your project includes auxiliary files which mislead
  the existing appMode inference. For example, if an HTML project includes
  a downloadable Shiny app.R, that content will be assumed to be a Shiny
  application even if that application is not meant to be run. (#948)

• appDependencies() accepts an appFileManifest argument as an alternate
  way of providing the target set of files.