Repository navigation
Conversation
* fix(frontend): remove canvas handle from connection_ref fields Connection references are set only through the connection picker and their value must never come from an edge. No output emits the connection_ref type, so the handle could never accept a connection, yet its tooltip invited drag/click and leaked the internal type name. * test(frontend): type proxy in createMockEdge helper instead of any Reuses FindPrimaryInputTemplate so Biome's noExplicitAny no longer fails the lint gate on this file.
* fix(deps): upgrade datamodel-code-generator datamodel-code-generator 0.71.0 -> 0.81.0 * fix(deps): upgrade Authlib security fixes authlib 1.8.0 -> 1.9.1 * fix(deps): upgrade Hono static path handling hono 4.13.8 -> 4.13.13 @hono/node-server 2.1.0 -> 2.1.5 * fix(deps): upgrade docs HTTP cache semantics http-cache-semantics (docs) 4.2.0 -> 4.3.0 * test: stabilize graph setup and cold flow upload regression * test: include cold upload regression in API and workspace suites --------- Co-authored-by: Eric Hare <ericrhare@gmail.com>
* test(files): verify unsafe renames preserve safe downloads * test(memories): isolate missing-resource handler checks
* fix(security): reject process and code loader capabilities * fix(security): block process signals and package importers
…b Search (#15769) * feat(mrscraper): consolidate bundle into three SDK tools * fix(mrscraper): update bundle release and loader expectations --------- Co-authored-by: riandradiva <riandra@mrscraper.com> Co-authored-by: Eric Hare <ericrhare@gmail.com>
* fix: show Slack and Microsoft list results in output inspector * chore: auto-bake note keys and regenerate backend locales/en.json [skip ci] * fix: refresh inspector representations for each output * docs: record output preview bundle contract * fix: bump Microsoft and Slack bundle versions * fix: synchronize Microsoft and Slack bundle profile versions --------- Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
* fix: preserve integration hints and codes in workflow errors * fix(workflow): retain hints from flat error blocks
* fix: persist connection health after runtime credential expiry * fix: preserve connections during transient OAuth refresh failures * fix(ci): parse complete migration revision declarations
…outages (#15775) * fix(integrations): report Google Workspace network failures accurately * chore: auto-bake note keys and regenerate backend locales/en.json [skip ci] * chore: trigger CI * fix(google): bump bundle version for network error changes * fix(ci): align Google bundle profile with patch release * fix(google): require compatible LFX releases without breaking nightlies * docs(lfx): document the network-error integration code --------- Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
* fix(slack): omit blank canvas titles from API requests * chore: auto-bake note keys and regenerate backend locales/en.json [skip ci] * fix(file): clarify encoding reporting in input help * [autofix.ci] apply automated fixes * fix(slack): bump bundle release metadata to 0.2.2 --------- Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
…(#15767) * fix(connections): validate pasted Slack tokens and credential health * fix(ci): parse complete migration revision declarations
…omes (#15766) * fix(connections): revoke pasted Slack tokens and report provider outcomes * docs: separate connection revocation guidance * fix(ci): parse complete migration revision declarations
* fix(connections): request offline access on Microsoft reconnect * fix(connections): preserve reconnect scopes across refetches
* fix(api): handle legacy NULL text in memory message listings * fix(api): normalize legacy NULL text in message updates
* fix(api): keep idle workflow streams alive * fix(api): keep public and reattached workflow streams alive
* fix(processing): preserve append and update payload keys * chore: auto-bake note keys and regenerate backend locales/en.json [skip ci] * fix(file): clarify standard and CSV encoding guidance * [autofix.ci] apply automated fixes --------- Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
* fix(agent): resolve current_date to the UTC day
The Agent filled {current_date} with a seconds-precision timestamp, so the system prompt changed on every turn. Provider prompt caching matches on the exact prefix, which meant the whole chat history after the system message was never served from cache. Resolve it to the ISO date, matching the "Today's date" label and the tool-calling agent.
* chore: auto-bake note keys and regenerate backend locales/en.json [skip ci]
* fix(agent): refresh bundled YouTube starter snapshot
* fix(bundles): bump version for refreshed YouTube starter
---------
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: Eric Hare <ericrhare@gmail.com>
…x (#15761)
* fix(mcp): keep a credential typed into the MCP component's Headers box
The MCP Tools component has a Headers input beside its server field, and its own
help text says those headers override the ones configured on the server. So it
is a reasonable place to put an Authorization header, and people do.
Packaging nulled it. The value is secret-named, so the scrubber removed it --
correctly, because a package is a file people store and share -- but nothing
declared a variable to put it back. The manifest named nothing, the deploy check
reported ready, and the deployed flow called the server with no header at all.
The failure surfaced as a 401 from someone else's service, with nothing anywhere
connecting it to a credential the deploy had removed.
Handled the same way as a credential in the server's own config, because the box
is the same shape as a config's `headers` map and the existing scrubber already
knows how to name one. Saving the flow moves the literal into a global variable
and leaves the generated name behind; packaging keeps that name and declares it;
the deploy refuses until the target has it.
Both storage shapes. The input is `DictInput(is_list=True)`, so the canvas stores
it as a mapping or as `{"key", "value"}` rows and the component reads either at
run time. Handling one and not the other would have missed half the flows.
Scoped to this component. The same nulling affects API Request, URL, Cloudflare
and Confluent Kafka Producer, and fixing those needs a decision this change
cannot make: an MCP server has a name to key the variable on and they do not.
Tracked separately.
What is deliberately still nulled: a literal that was never rewritten, a name
that is not the one this server and field generate, every value when the reader
has no variable manifest (a public share), and anything the ordinary rules
catch -- a credential inside a URL under an innocent header name, or one nested
deeper in a value.
Four defects in earlier drafts of this change were found by open-code-review and
each reproduced before being fixed:
- Skipping the generic pass for the whole field switched off scrubbing it was
doing. A URL carrying credentials under a non-secret header name survived.
References are now lifted out, the ordinary scrub runs, and they go back --
the shape `_strip_table_rows_in_place` already uses.
- The row form of the box was skipped entirely at save time.
- The box and the server config generated the same variable name, so whichever
was written last won. In practice the config, which silently discarded the
override -- the one thing the box exists to do. Both sides now derive from
`mcp_header_scope`.
- Save time rewrites every header outside `NON_SECRET_HEADERS`; packaging only
kept the ones `_is_secret_name` matched, so `X-Tenant` got a generated name
that nothing declared and nothing would resolve.
Found by QA against MCP Tools. Not a regression: this path has behaved this way
independently of recent deployment work.
* fix(mcp): isolate header overrides and reject missing bindings
* fix(mcp): only treat a credential-named header as a credential
CI caught this: `test_public_flow_read_strips_secrets` asserts a non-secret
header survives a public read, and it stopped surviving.
X-Tenant: acme
before this commit -> MCP_TENANT_MCP_HEADER_OVERRIDE_X_TENANT_9EFC07A6
after -> acme
Authorization: Bearer ghp_real
unchanged -> MCP_GITHUB_HEADER_OVERRIDE_AUTHORIZATION_4B0ECCD7, declared
The two halves of the Headers-box handling disagreed about which headers are
credentials, and I resolved it the wrong way round. Save time was widened to the
rule a *server config* follows -- everything outside `NON_SECRET_HEADERS` is a
secret -- which is right there, because a config is a connection's own
credentials. Applied to the component's Headers box it swept up ordinary routing
headers, so a tenant id became a variable somebody had to provision on the
serving plane for a value that is not a secret.
Narrowed instead: both halves now ask `is_secret_header_name`, one predicate so
they cannot drift apart again. A header that does not read as a credential is
left alone at save and at packaging, which is what that test has always said
should happen.
The test I added asserting the opposite is replaced by one asserting this.
Found by CI in a directory my own sweep skipped. The test reaches this code
through `langflow.api.utils.core`, so it names neither the function I edited nor
its module, and no grep for either would have found it. Grepping for the public
names the module exports does; that is how the 14 files run for this commit were
chosen, 600 passing.
---------
Co-authored-by: Janardan S Kavia <janardanskavia@Janardans-MacBook-Pro.local>
Co-authored-by: Eric Hare <ericrhare@gmail.com>
fix(connections): add provider setup guidance on 1.13
- 统一生产配置模板,补充认证、HTTPS、CORS、连接池和任务运行参数 - 新增同机 PostgreSQL/pgvector、Redis、SeaweedFS S3 配置及测试覆盖项 - 修正数据目录权限和 S3 path-style 配置 - 补充部署流程、多实例共享配置约定及待完成事项 - 更新镜像版本至 0.1.2
- 将 Playwright 和无障碍扫描运行环境固定为 Ubuntu 24.04 - 调整 PR 标题校验规则,支持中文描述 - 补充 PR 标题格式回归测试
- 为提供商列表添加独立滚动区域,保持搜索框固定 - 调整弹窗与设置页高度约束,改善矮窗口下的显示 - 根据输入框实际状态控制提示显示,兼容自动填充及预览
- Add a responsive homepage with glass styling, particle waves, and animated workflow previews - Support light and dark themes, eight languages, and scroll-aware navigation - Add animation controls, reduced-motion support, and offscreen animation suspension - Simplify homepage copy and remove punctuation from headings - Optimize canvas rendering, blur effects, and pointer and scroll updates - Initialize themes before first paint to prevent startup flicker - Serve the public homepage at / and update workspace navigation and auth redirects to /flows - Expand homepage, theme, authorization, and accessibility regression coverage - Enable branch CI, extend PR triggers, deduplicate runs, and refine change filtering - Parallelize Jest with transform caching and merged coverage - Optimize Playwright sharding and retain traces for failed tests - Add CI scheduling tests and update workflow documentation
Merge official 260cbf3 while preserving OpenXFlow branding, channels, RBAC, provider compatibility and release gates. Resolve 75 conflicts, regenerate combined lockfiles and component metadata, and join the upstream authentication and OpenXFlow Alembic heads with a no-op merge revision that preserves existing data. Validation: frontend build and TypeScript; 558 Jest tests; 267 LFX flow checks; 154 API migration/recovery tests; SQLite upgrade/data preservation; 804 focused CI/Docker checks; 72 security dependency checks. Seven Windows shell/path/newline harness cases still fail in the raw CI script run. External database/provider prerequisites and browser/image acceptance remain outside the completed local checks.
… merge - Align the Python test matrix with supported package versions - Fetch historical release tags from the official upstream repository - Fix the Docker joserfc pin conflicting with workspace constraints - Align backend branding assertions and Agent template source hashes - Fix database listener cleanup and SQLite pool test compatibility - Update dependency constraint tests while retaining security checks - Fix frontend redirect, external link, and paginated deletion assertions - Add workflow and Docker dependency constraint regression coverage
Mock SSRF client helpers at both import locations to prevent real DNS lookups during model construction while preserving production SSRF protection. Validated with 237 passing provider, model initialization, and SSRF tests.
- Reuse CI script tests across branch and PR workflows - Run the full CI suite for upstream sync branches - Generate component dependency versions from uv.lock - Update the joserfc security pin assertion and component index - Add PR readiness guidelines, a checklist, and regression tests
- Clean up flows and saved components through the authenticated API - Verify the inventory is empty before reloading the page - Add regression coverage for empty inventories and cleanup failures
- prevent AuthModal input from leaking across Jest tests - fix manual-login reload redirect loops in Playwright - refresh expired users after database session rollbacks - clean up requests abandoned during document navigation - add regression tests and frontend CI guidance
- add backend preflight checks before the full test matrix - isolate process integration tests from parallel shards - prevent performance reports from duplicating test failures - increase process readiness timeout for loaded CI runners - limit release workflows to supported Python 3.10–3.14 - add CI contract tests for the new workflow constraints
chore(sync): integrate Langflow 1.13.2 into OpenXFlow
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Contributor
✅ Test Coverage AdvisorNo source changes detected without accompanying tests. Thanks for keeping coverage up! 🎉
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
1 similar comment
This comment has been minimized.
This comment has been minimized.
Contributor
- 限定审计导出连接统计范围,避免后台任务引起误报 - 隔离内存摄取测试数据库,避免 SQLite 锁竞争 - 更新 Soup Sieve 依赖约束与锁文件,补充 Python 版本边界测试
This comment has been minimized.
This comment has been minimized.
1 similar comment
Contributor
|
Build successful! ✅ |
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.
Summary
Promote the current
developbranch tomainand prepare the OpenXFlow0.1.2production release.This release:
main.Validation
maindevelopbb72a1d67f06db96c36c1d443bf88de1a1ae17438 passed58 passed733 passedPR readiness
maintarget is intentional for this production promotion.mainPR.developandmainPR checks before merging.Deployment notes
0.1.2mainimage tag is promoted only from the verified digest.SECRET_KEYcontinuity before deployment.