Rsconnect-python

Added
- Added support for deploying Shiny express apps.
- Added support for deploying Shiny Express applications.
- Added a `--retry` flag to the `rsconnect content build run` command to re-run
builds for all content in the NEEDS_BUILD, ABORTED, ERROR, or RUNNING state.

Changed
- Improved the error and warning outputs when options conflict by providing the source
from which the values have been determined. This allows for faster resolution of issues
when combinations of stored credentials, environment variables and command line options
are used.
- Updated verbose mode to output the source of all options being used when processing the
CLI command.

Fixed
- Interrupting a long-running `rsconnect content build run` command with `^C`
will now update the local state file before attempting graceful cleanup. This
should help prevent users from getting stuck a "build already running" state.
See [467](https://github.com/rstudio/rsconnect-python/issues/467) for details.

- Addressed an error which occurred when attempting to create manifests for
Quarto documents. (534)

Fixed
- The `https_proxy` environment variable is recognized as a synonym for
`HTTPS_PROXY`.
- When adding a new server, the initial request now includes an
authorization header containing the API key. This is needed
for Connect installations behind a proxy that only passes
authenticated requests.
- Common environment directories (`env, venv, .env, .venv`) are no longer
excluded by name. Environments are detected by the presence of a python
executable in `bin` or `Scripts` and excluded.
- Lines output from `pip freeze` which start with [notice] are filtered out from the generated `requirements.txt`.

Added
- Added support for the `no_proxy` or `NO_PROXY` environment variables to specify
hosts that should not be accessed via proxy server. It's a comma-separated list
of host or domain suffixes. For example, specifying `example.com` will
bypass the proxy for example.com, host.example.com, etc.
- If an entrypoint is not specified with `--entrypoint`, rsconnect-python will try
harder than before to choose an entrypoint file. In addition to the previously
recognized filename patterns, the file patterns `app-*.py`, `app_*.py`, `*-app.py`,
and `*_app.py` are now considered. However, if the directory contains more than
one file matching these new patterns, you must provide rsconnect-python with an
explicit `--entrypoint` argument.
- Added a new verbose logging level. Specifying `-v` on the command line uses this
new level. Currently this will cause filenames to be logged as they are added to
a bundle. To enable maximum verbosity (debug level), use `-vv`.
- Added a verification step to the deployment process that accesses the deployed content.
This is a `GET` request to the content without parameters. The request is
considered successful if there isn't a 5xx code returned (errors like
400 Bad Request or 405 Method Not Allowed because not all apps support `GET /`).
For cases where this is not desired, use the `--no-verify` flag on the command line.
- Added the `deploy flask` command.
- Added the `write-manifest flask` command.

Changed
- Removing experimental support for Conda. Connect does not support restoring Conda environments.

Fixed
- Python virtualenvs are now detected in Windows environments, and are automatically
excluded from the uploaded bundle.
- Error deploying to shinyapps.io when `--app-id` is provided [464](https://github.com/rstudio/rsconnect-python/issues/464).

Added

- Add `--disable-env-management`, `--disable-env-management-py` and `--disable-env-management-r` flags for all content types
that support environment restores. These flags indicate to Connect that the user is responsible for Python/R package
installation, and Connect should not install packages during the build. The Python/R packages must still be available in the runtime
environment in order to run the content. This is especially useful if off-host execution is enabled when the execution environment
(specified by `--image`) already contains the required packages. Requires Posit Connect `>=2023.07.0`.

Added
- Failed deploys to shinyapps.io will now output build logs. Posit Cloud application deploys will also output build logs once supported server-side.
- Redeploy to Posit Cloud from a project now correctly associates the content with that project.

Added

- The `CONNECT_TASK_TIMEOUT` environment variable, which configures the timeout for [task based operations](https://docs.posit.co/connect/api/#get-/v1/tasks/-id-). This value translates into seconds (e.g., `CONNECT_TASK_TIMEOUT=60` is equivalent to 60 seconds.) By default, this value is set to 86,400 seconds (e.g., 24 hours).
- Deploys for Posit Cloud now support Quarto source files or projects with `markdown` or `jupyter` engines.

Added
- Deploys for Posit Cloud and shinyapps.io now accept the `--visibility` flag.

Changed
- Removes redundant client-side compatibility checks in favor of server-side compatibility checks when deploying Python content. Note that the error handling may differ between versions of Connect. See Connect release notes for additional details regarding compatibility.