Langflow release notes - Langflow

import Icon from "@site/src/components/icon"; import McpIcon from '@site/static/logos/mcp-icon.svg';

This page summarizes significant changes to Langflow in each release. For all changes, see the Changelog.

Due to strict SemVer requirements, Langflow Desktop can have different patch versions than the core Langflow OSS Python package, but the major and minor versions are aligned.

Prepare to upgrade

:::warning Whenever possible, the Langflow team recommends installing new Langflow versions in a new virtual environment or VM before upgrading your primary installation. This allows you to import flows from your existing installation and test them in the new version without disrupting your existing installation. In the event of breaking changes or bugs, your existing installation is preserved in a stable state. :::

To avoid the impact of potential breaking changes and test new versions, the Langflow team recommends the following upgrade process:

Recommended: Export your projects to create backups of your flows:

bash

curl -X GET \
"$LANGFLOW_SERVER_URL/api/v1/projects/download/$PROJECT_ID" \
  -H "accept: application/json" \
  -H "x-api-key: $LANGFLOW_API_KEY"

To export flows from the visual editor, see Import and export flows.

Install the new version:
- Langflow OSS Python package: Install the new version in a new virtual environment. For instructions, see Install and run the Langflow OSS Python package.
- Langflow Docker image: Run the new image in a separate container, or upgrade your existing image. For more information, see Upgrade the Langflow Docker image.
- Langflow Desktop: To upgrade in place, open Langflow Desktop, and then click Upgrade Available in the Langflow header. If you want to isolate the new version, you must install Langflow Desktop on a separate physical or virtual machine, and then import your flows to the new installation.
Import your flows to test them in the new version, upgrading components as needed.

When upgrading components, you can use the Create backup flow before updating option if you didn't previously export your flows.
If you installed the new version in isolation, upgrade your primary installation after testing the new version.

If you made changes to your flows in the isolated installation, you might want to export and import those flows back to your upgraded primary installation so you don't have to repeat the component upgrade process.

1.10.x

Highlights of this release include the following changes. For all changes, see the Changelog.

Deprecations

Voice mode is removed

The <Icon name="Mic" aria-hidden="true"/> Microphone button in the Playground now only enables speech-to-text, with no additional voice mode functionality. The bi-directional /v1/voice/ws/flow_as_tool/{flow_id} voice-to-voice endpoints are deprecated. For more information, see Use voice mode.

1.9.x

For 1.9.x release notes, see the 1.9.x documentation.

1.8.x

For 1.8.x release notes, see the 1.8.x documentation.

Earlier releases

See the Changelog.