Langflow release notes

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:

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

   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.

2. 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.

3. 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.

4. 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.13.x

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

Breaking changes

• Official packages require authentication by default

  Official Python packages, tagged source archives, and Docker images now set LANGFLOW_AUTO_LOGIN=false. Set LANGFLOW_SUPERUSER_PASSWORD, then sign in as langflow or the username in LANGFLOW_SUPERUSER.

  Before upgrading an auto-login installation, prepare that account for password sign-in.

  If you already upgraded and can't sign in, see recover access.

  For more information, see API keys and authentication.

• Chroma and Local DB components are removed

  Langflow 1.13 stores local Knowledge and Memory in SQLite, instead of a local Chroma database. The Chroma DB and Local DB components are legacy.

  Replace Chroma and Local DB with a knowledge base, or with a supported remote vector store.

  For more information, see Upgrade Knowledge and Memory storage.

New features

• Audit logging

  Set LANGFLOW_AUDIT_ENABLED=true to record an append-only history of flow and project operations, including who attempted a change, on which resource, when, how it completed, and a description of what was written. Query events with GET /api/v1/flows/audits and GET /api/v1/projects/audits.

  For more information, see Audit logging.

• Connections

  Langflow stores Google Workspace, Microsoft 365, and Slack accounts as persistent connections. For more information, see Connections.

• Concurrent editing

  Langflow now protects a flow that is open by more than one user. For more information, see Concurrent editing.

• Instance migration

  Langflow provides a guided workflow to migrate users, projects, flows, settings, local files, and local knowledge bases to a new instance. The workflow checks the source instance, pauses writes, creates a backup, copies applicable data to the target instance's storage, verifies the copy, and provides recovery steps.

  For more information, see Migrate a Langflow instance.

• Administration API and CLI

  Superusers can manage users, teams, and roles with the API or the langflow admin command. For more information, see Administer users and teams with the API and CLI.

Component changes

• The ALTK component is removed

  The ALTK component is removed.

  Replace ALTK with the Agent component.

• MrScraper components are removed

  The MrScraper bundle now provides three components.

  Instead, use the Scraper API or Web Search components.

  For more information, see Update existing flows.

1.12.x

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

1.11.x

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

1.10.x

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

1.9.x

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

Earlier releases

See the Changelog.