Langflow follows a release-when-ready cadence, with each cycle typically lasting 4–6 weeks depending on QA and stabilization needs.
- Keep
mainfast-moving for everyday work while ensuring stable release builds when features mature. - Provide an isolated branch for QA and last-minute fixes (the release candidate, RC).
- Preserve a linear, readable history wherever possible.
- Ensure released code is extensively tested before publication.
- Minimize time to resolution of critical bugs.
Create an OSS release candidate (RC) branch containing langflow and any associated PyPI packages (e.g. lfx).
During this period:
- QA is performed manually.
- Bug fixes are merged into the RC branch.
- New features continue development on
main.
This step usually lasts about a week.
Once OSS QA and bugfixing are complete, create a Desktop release candidate.
- The Desktop RC is based on the final OSS RC.
- Manual QA is performed.
- Bug fixes are merged into the Desktop RC.
- New features continue on
main.
This step also usually lasts about a week.
After QA and bugfixing are complete for both OSS and Desktop:
- Final releases are cut from their respective RC branches.
- Release timing is coordinated with Langflow's DevRel team.
- For at least 24 hours after release, Discord, GitHub, and other support channels should be monitored for critical bug reports.
The release workflow automatically publishes the following artifacts:
-
PyPI Packages:
langflow- Main package with all integrationslangflow-base- Core framework without integrationslfx- Lightweight executor CLIlangflow-sdk- SDK for programmatic access (when updated)
-
Docker Images:
langflowai/langflow- Full Langflow imagelangflowai/langflow-backend- Backend-only image (published independently)langflowai/langflow-frontend- Frontend-only image (published independently)langflowai/langflow-ep- Enterprise edition image (published independently)langflowai/langflow-base- Base image without integrations
Note: Backend, frontend, and enterprise images are published separately from the main image and will be built even if the main version already exists on Docker Hub.
| Branch | Purpose | Merge Policy |
|---|---|---|
main |
Integration branch. All feature PRs target this by default. | Squash & Merge (linear history) |
release-X.Y.Z(e.g. release-1.4.3) |
Temporary RC branch. Active only for the release cycle. Accepts QA and blocking-bug PRs labeled type:release. |
Squash & Merge within the branch. Rebased onto main before final merge. |
git checkout main && git pull # Ensure local main is up to date
git checkout -b release-X.Y.Z # Create new release candidate branch
git push -u origin release-X.Y.Z # Push RC branch to remote- Create a feature branch as usual.
- Open a GitHub PR targeting
release-X.Y.Z. - Review and approve as normal.
- Merge into the RC branch after review.
Before tagging, review regressions/X.Y.x.yaml to confirm no unresolved blocking entries exist.
If blocking entries exist, they should be signed off on.
See regressions/README.md for the full schema and entry instructions.
Use the prepared release-tag process so published source archives, wheels and images disable automatic login while development branches retain it.
- Finish version updates and fixes on
release-X.Y.Z. - Run Prepare Release Tag with
tag=vX.Y.Zandref=release-X.Y.Z. If an earlier candidate already uses this tag and the source has changed, enablereplace_prepared_tag. The workflow verifies the existing preparation, protects final GitHub releases and checks for concurrent tag updates. - Run the normal release workflow with
release_tag=vX.Y.Z,release_commitset to the full prepared SHA, andpre_releasedisabled. The workflow reserves a draft final release before publishing packages or images, even whencreate_release=false. Keep that reservation if publication fails and retry the same source commit.
Use the same preparation process before each release candidate. Do not create tags directly on the release branch or move published final tags; publish a new version for subsequent fixes. Keep the authentication-preparation commit out of the branch merged back into main.
git checkout main
git merge --ff-only release-X.Y.Z # Fast-forward main to include RC changes-
Squash & Merge everywhere for atomic commits and clean history.
-
While RC is open, periodically re-sync with main:
git checkout release-X.Y.Z git fetch origin git rebase origin/main
This resolves conflicts early while keeping history linear.
-
Final merge back must be fast-forward only. If not possible, rebase the RC onto
mainbefore merging.
- Follows Semantic Versioning:
MAJOR.MINOR.PATCH. - RC tags use
-rc.N, e.g.v1.8.0-rc.1. - All tags MUST start with
vprefix (e.g.,v1.9.1, not1.9.1).- The release workflow validates this format and rejects tags without the
vprefix. - Duplicate tags (e.g., both
1.8.3andv1.8.3) cause GitHub's release notes generation to use the wrong base comparison, resulting in incomplete changelogs. - The workflow automatically checks for and prevents duplicate tags.
- The release workflow validates this format and rejects tags without the
Langflow and LFX share a major.minor version line. The compatibility contract is:
LFX X.Y.N is guaranteed compatible with any Flow exported from Langflow X.Y.M.
Patch releases (N and M) are independent — a patch to LFX does not require a Langflow patch release, and vice versa.
make patch v=X.Y.Z updates all four artifacts together:
| Artifact | Version set |
|---|---|
langflow |
X.Y.Z |
langflow-base |
0.Y.Z |
lfx |
X.Y.Z |
| frontend | X.Y.Z |
Use scripts/release-lfx.sh <version>. The script warns if the LFX minor version does not match the current Langflow minor version, which would violate the compatibility contract. A warning is not a hard block — patch-only LFX releases within the same minor are expected and fine.
Users can pin lfx~=X.Y.0 in their requirements.txt to receive all compatible LFX patch releases for a given Langflow minor.
LFX was realigned from its standalone 0.5.x line onto Langflow's major.minor line, so the version jumps from 0.5.0 to 1.10.0 in a single step. This is a version-numbering change, not 95 minors of feature churn. The jump affects downstream pins, and neither pip nor uv will flag it — so it must be called out in the release announcement, not just here:
lfx==0.5.xorlfx<1.0pins will not upgrade (intentional — those deployments stay put).lfx>=0.5,<1pins will not upgrade.lfx>=0.5with no upper bound will pull1.10.0on the next install — a major jump with no warning.
Going forward, pin lfx~=X.Y.0 (e.g. lfx~=1.10.0) so you track compatible patches for a given Langflow minor without silently crossing minor lines.
| Role | Responsibility |
|---|---|
| Release Captain (rotates per cycle) | Owns timeline, branch cut, tagging, merge-back. |
| PR Author | Ensures tests pass; flags PR with type:release if needed in RC. |
| CI | Blocks merges on failing tests or missing labels. |
No. Always rebase the RC onto main to preserve linear history.
Not yet — merge-back and cleanup are manual.
Very flexible. QA and stabilization phases can be extended as needed for quality.