Repository navigation
Publish the Langflow extension independently - #1007
Merged
Merged
Conversation
Build and check the extension archives, qualify installed discovery with published SDK dependencies, and publish checked artifacts through package-specific trusted publishing. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changelog category
Changelog entry
The Langflow extension has an independent PyPI publication workflow with package-specific version tags and installed extension checks.
Why
lfx-loomhas its own version and extension entry point. Its package needs a publication path separate from the server release artifacts.Scope and risk
The workflow builds and checks the wheel, source distribution and rebuilt wheel. It checks the installed extension with published SDK 1.2.0 and normal dependency resolution, records the resolved SDK version, and verifies LFX discovery without invoking a component or a live flow. Only the publication job can obtain an OIDC token, and it publishes the checked artifacts.
The tag must exactly match the stable version in both manifests and point to a commit on main. The package-specific PyPI publisher and GitHub environment need configuration; their availability has not been verified. The source package version remains 0.1.0.
Compatibility, rollout and rollback
No wire fields, stored rows, runtime settings or migrations change. Configure PyPI trusted publishing for
ClickHouse/loom, workflowlangflow-publish.yml, environmentpypi-lfx-loom, then follow the normal immutable tag procedure after review and CI. Reverting the workflow stops future uploads; published files remain immutable.Tests
Ruff format/check, the prose check and
git diff --checkpass. The 13 direct publication-guard/main-ancestry cases and eight existing archive-regression cases pass: 21 tests in 2.80 seconds. Earlier local attempts stopped before workload admission and are not test results.Hosted build, source-archive rebuild and both installed-discovery jobs passed. Both SDK 1.2.0 and current dependency resolution installed SDK 1.2.0 and discovered extension 0.1.0 through LFX 1.13.3. No live component or flow was invoked, and no package was published.
Required CI first failed the existing Java parser cost guard: fan-out definitions measured 8.50901x and the larger parse timed out. Parser, harness and locked dependency sources match a naturally successful main run. One rerun of the failed job and its dependent coverage job passed, and all required hosted CI checks completed successfully for this commit. The timing failure's cause remains unknown; the rerun does not establish that it was flaky. No parser, timing-budget, assertion or skip change is included.
AI assistance in the code
AI-generated: Codex wrote the workflow, direct publication-guard tests and procedure. Source review checked the artifact flow, permissions, tag/manifest matching and use of the existing extension checks. Hosted build and installed-discovery results are listed above.
I can explain every line of this diff and how it interacts with the rest of Loom.
Checklist