Files
langflow/docs
Eric Hare 7266606578 Merge branch 'release-1.11.0' into bundles/foundation-discovery
Resolve conflicts from NextPLAID bundle (#13553) landing on release-1.11.0
while this branch restructured bundles into the metapackage split (Phase A).

Union resolution across the three conflicting files — keep every
metapackage-split bundle (lfx-bundles[all] long tail + graduated partners
datastax/openai/anthropic/amazon/cohere/oracle) and add lfx-nextplaid as a
standalone bundle, matching the oracle (#13502) precedent:

- pyproject.toml: add lfx-nextplaid to deps (bounded >=0.1.0,<1.0.0), sources
  (workspace), and workspace members.
- migration_table.json: append NextPlaid/Vllm-multivector entries (exact match
  with release-1.11.0); complete the trailing oracle entry. Loads via lfx
  loader, 416 entries.
- uv.lock: add lfx-nextplaid + langchain-plaid; verified with `uv lock --check`.

Also type the NextPLAID-era CanvasControlButton test mocks (replace `any`) so
the merge passes the biome pre-commit hook.

NextPLAID adds no component_index/locale/starter-project changes (ext bundle),
so nothing generated needs regeneration.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-16 10:04:27 -07:00
..
2025-02-06 17:44:46 +00:00

Website

This website is built using Docusaurus 3, a modern static website generator.

Installation

$ npm install

Local Development

$ npm run start

This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.

Build

$ npm run build

This command generates static content into the build directory and can be served using any static contents hosting service, including npm run serve.

Import code snippets from the repo

To embed source files directly in the docs, use raw-loader to import the file as a string and pass it to the native CodeBlock component.

import CodeBlock from "@theme/CodeBlock";
import customComponent from "!!raw-loader!@langflow/src/lfx/src/lfx/custom/custom_component/custom_component.py";

<CodeBlock language="python" title="CustomComponent metadata (from codebase)">
  {customComponent}
</CodeBlock>

Docusaurus Versioning

The versioning configuration is found in docusaurus.config.js.

Versioning example for release version 1.9.x on top of 1.8.x:

  1. Before release, the docs in the active release branch should already be set to 1.8.x, the current version.
  2. When ready to release 1.9.x, create a branch and run npm run docs:version -- 1.9.0 to snapshot the current docs.
  3. After creating a new version, update docusaurus.config.js to include the 1.9.0 release:
docs: {
  lastVersion: '1.9.0',
  versions: {
    '1.9.0': {
      label: '1.9.x',
      path: '1.9.0',
    },
    '1.8.0': {
      label: '1.8.x',
      path: '1.8.0',
    },
  },
},
  1. Test the deployment locally:
npm run build
npm run serve
  1. Create a pull request to main, and merge to create your new release.
  2. To create version 2.0.x, repeat the process: update the active release branch docs to 2.0.x when you begin working on it, then when ready to release, run npm run docs:version -- 2.0.0, update docusaurus.config.js with labels using .x notation, and merge to main.
  • lastVersion = the most recent released version (shown as "latest" in the UI).

See the Docusaurus docs for more info.

Disable versioning

  1. Remove the versions configuration from docusaurus.config.js.
  2. Delete the docs/versioned_docs/ and docs/versioned_sidebars/ directories.
  3. Delete docs/versions.json.

References

Deployment

Using SSH:

$ USE_SSH=true npm run deploy

Not using SSH:

$ GIT_USER=<Your GitHub username> npm run deploy

If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the gh-pages branch.