mirror of
https://github.com/langflow-ai/langflow.git
synced 2026-07-24 00:03:32 +08:00
7c347a56ea
* docs-1.10-release-notes-and-link-out-to-previous-versions * docs-remove-outdated-windows-upgrade-note
128 lines
7.2 KiB
Plaintext
128 lines
7.2 KiB
Plaintext
---
|
|
title: Langflow release notes
|
|
slug: /release-notes
|
|
---
|
|
|
|
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](https://github.com/langflow-ai/langflow/releases/latest).
|
|
|
|
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](/concepts-flows-import#import-a-flow) 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.
|
|
If you are upgrading Windows Desktop to 1.6.0, don't auto-upgrade with the in-app **Update** button. Instead, follow the instructions in [Known issue: Don't auto-upgrade Windows Desktop](#windows-desktop-update-issue).
|
|
:::
|
|
|
|
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](/api-projects#export-a-project) 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](/concepts-flows-import).
|
|
|
|
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](/get-started-installation#install-and-run-the-langflow-oss-python-package).
|
|
* **Langflow Docker image**: Run the new image in a separate container.
|
|
* **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](/concepts-flows-import) to the new installation.
|
|
|
|
3. [Import your flows](/concepts-flows-import) to test them in the new version, [upgrading components](/concepts-components#component-versions) 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.9.x
|
|
|
|
Highlights of this release include the following changes.
|
|
For all changes, see the [Changelog](https://github.com/langflow-ai/langflow/releases).
|
|
|
|
### New features and enhancements
|
|
|
|
- Langflow MCP client for Bob (IBM) and Claude Code
|
|
|
|
The **Settings** page now includes <Icon name="Terminal" aria-hidden="true"/> **Langflow MCP Client**, with instructions to connect **Bob (IBM)** and **Claude Code** to your Langflow instance.
|
|
For more information, see [Langflow MCP client](../Agents/langflow-mcp-client.mdx).
|
|
|
|
- MCP Tools: register servers first, and then add from the MCP sidebar
|
|
|
|
**MCP Tools** is no longer added from the **Agents** component list. Register each MCP server under **Settings** > **MCP Servers*, or from the flow editor <McpIcon /> **MCP** sidebar.
|
|
Each saved server appears as a unique **MCP Tools** component that can be dragged to the canvas.
|
|
For more information, see [Use Langflow as an MCP client](/mcp-client#use-the-mcp-tools-component).
|
|
|
|
- Flow DevOps Toolkit SDK
|
|
|
|
Use the Flow DevOps Toolkit SDK to manage local and remote flows with Git-style terminal commands.
|
|
For more information, see the [Langflow Flow DevOps Toolkit SDK](../API-Reference/flow-devops-sdk.mdx).
|
|
|
|
- Renamed `Data` and `DataFrame` types
|
|
|
|
The `Data` object is now named `JSON`, and the `DataFrame` object is now named `Table`.
|
|
Flows using `Data` or `DataFrame` are backwards compatible.
|
|
For more information, see [Langflow data types](/data-types).
|
|
|
|
- Renamed **Data Operations** and **DataFrame Operations** components
|
|
|
|
The **Data Operations** component is now the [**JSON Operations** component](/data-operations), and the **DataFrame Operations** component is now the [**Table Operations** component](/dataframe-operations).
|
|
|
|
- Flow version history in the visual editor
|
|
|
|
You can now save point-in-time versions of a flow from **Version History**, preview saved versions in read-only mode, and restore an earlier version to your working draft.
|
|
For more information, see [Build flows](../Flows/concepts-flows.mdx#save-and-restore-flow-versions).
|
|
|
|
- Enabled tool calling for Gemini 3 preview models
|
|
|
|
Tool calling is enabled for the following Google Gemini 3 preview models:
|
|
`gemini-3.1-pro-preview`, `gemini-3-pro-preview`, `gemini-3-flash-preview`, and `gemini-3-pro-image-preview`.
|
|
|
|
- Build components with **Langflow Assistant**
|
|
|
|
**Langflow Assistant** is a graph-aware co-pilot that can create components from natural language prompts, directly within the Langflow workspace.
|
|
For more information, see [Langflow Assistant](../Flows/langflow-assistant.mdx).
|
|
|
|
- Vulnerability reporting now uses HackerOne
|
|
|
|
Security reports should now be filed through [IBM's HackerOne program](https://hackerone.com/ibm).
|
|
Please do not report security vulnerabilities through public GitHub issues or GitHub security advisories.
|
|
For the full policy and what to include in a report, see the [Langflow Security Policy](https://github.com/langflow-ai/langflow/blob/main/SECURITY.md).
|
|
|
|
- Disable custom components
|
|
|
|
Set `LANGFLOW_ALLOW_CUSTOM_COMPONENTS=false` to disable custom components and in-editor editing of component code.
|
|
For more information, see [Block custom components](../Deployment/deployment-block-custom-components.mdx).
|
|
|
|
- Deploy flows to watsonx Orchestrate (beta)
|
|
|
|
In Langflow 1.9.1, Langflow flows can now be published to IBM watsonx Orchestrate as tools that a watsonx Orchestrate agent can call.
|
|
This workflow packages a selected flow version for use in IBM watsonx Orchestrate.
|
|
For more information, see [Deploy Langflow on watsonx Orchestrate](../Deployment/deployment-wxo.mdx).
|
|
|
|
As of Langflow 1.9.2, this feature is behind a feature flag. To enable it, set `LANGFLOW_FEATURE_WXO_DEPLOYMENTS=true` before starting Langflow.
|
|
|
|
- **Policies** component (beta)
|
|
|
|
The **Policies** component uses [ToolGuard](https://github.com/AgentToolkit/toolguard) to generate guard code from natural-language business policies and apply it to agent tools.
|
|
For more information, see [Policies (Beta)](../Components/policies.mdx).
|
|
|
|
## 1.8.x
|
|
|
|
For 1.8.x release notes, see the [1.8.x documentation](https://docs.langflow.org/1.8.0/release-notes).
|
|
|
|
## Earlier releases
|
|
|
|
See the [Changelog](https://github.com/langflow-ai/langflow/releases). |