Ferro Labs

August 29, 2026 · View on GitHub

Sibling packages that adapt ferrolabsai into popular AI frameworks. Each sub-folder is an independently versioned, independently published Python package.

PackageFolderPyPI
langchain-ferrolabsailangchain-ferrolabsai/https://pypi.org/project/langchain-ferrolabsai/
llama-index-llms-ferrolabsaillama-index-llms-ferrolabsai/https://pypi.org/project/llama-index-llms-ferrolabsai/

Why a sub-folder layout?

  • One repo, one issue tracker, one CHANGELOG section per integration.
  • Each integration declares its own version + dependency pin on ferrolabsai.
  • CI publishes each package independently when its folder's pyproject.toml version is bumped and a matching tag is pushed (e.g. langchain-ferrolabsai-v0.1.0).
  • Mirrors the pattern used by Anthropic, Cohere, and the LangChain monorepo's libs/partners/.

Building & publishing locally

cd integrations/langchain-ferrolabsai
python -m build
twine upload dist/*

CI workflows for each package live under .github/workflows/publish-<package>.yml (publish-langchain-ferrolabsai.yml, publish-llama-index-llms-ferrolabsai.yml): they run the sub-package's test matrix on PRs touching its folder and publish via Trusted Publishing on a matching tag.

Upstream mirroring

  • llama-index-llms-ferrolabsai — once stable, mirror as a PR to run-llama/llama_index under llama-index-integrations/llms/llama-index-llms-ferrolabsai/. Merge auto-publishes to PyPI.
  • langchain-ferrolabsai — third-party publication is fine; optionally open a PR to langchain-ai/langchain under libs/partners/ferrolabsai/ for first-party discoverability.