chore: Resolve master→3.x sync conflict - #37244
Merged
Merged
Conversation
…36914) Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: Matsuuu <16068444+Matsuuu@users.noreply.github.com>
…grade (#36984) Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
…service (no-changelog) (#36918)
…no-changelog) (#34436) Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
…ck when full screen (#36930)
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
…tions (#36898) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
…low (#37023) Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
…37031) Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
… update (no-changelog) (#36981)
…tests (no-changelog) (#37220) Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
…l picker (#37143) Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
…ement (no-changelog) (#37223) Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
…gelog) (#37119) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com> Co-authored-by: n8n-cat-bot[bot] <n8n-cat-bot[bot]@users.noreply.github.com>
…lls (#37159) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
…ation code + PKCE) (#37007)
# Conflicts: # .code-health-baseline.json # packages/@n8n/nodes-langchain/nodes/agents/Agent/agents/ConversationalAgent/execute.ts # packages/@n8n/nodes-langchain/nodes/agents/Agent/agents/ReActAgent/execute.ts # packages/@n8n/nodes-langchain/nodes/vector_store/VectorStoreSupabaseInsert/VectorStoreSupabaseInsert.node.ts # packages/@n8n/nodes-langchain/nodes/vector_store/VectorStoreSupabaseLoad/VectorStoreSupabaseLoad.node.ts # pnpm-lock.yaml
…mat) - Delete ConversationalAgent/ReActAgent execute.ts + test: Agent v1 was removed on 3.x (#36315); master's error-handling tweaks (#37113, #31499) apply only to the removed files (surviving ToolsAgent V2/V3 changes merged cleanly) - Delete VectorStoreSupabaseInsert/Load nodes: removed as dead nodes on 3.x (#34327); shared/supabase.ts stays (used by VectorStoreSupabase) - .code-health-baseline.json: take master's format (no generated/totalViolations header) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Bundle ReportChanges will increase total bundle size by 59.96kB (0.1%) ⬆️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: editor-ui-esmAssets Changed:
|
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
Contributor
Instance AI Discovery Eval ✅Branch: Eval output |
Contributor
Performance Comparison🔴 1 regression · ✅ 8 ok · current → latest master → 30-day baseline Needs attention
Full results (9 metrics across 5 benchmarks)Idle baseline · memory
loads S-tier workflow @tier:S
Idle baseline · instance-ai
Idle baseline · agents
docker-stats
How to read this table
|
Flexicon
approved these changes
Aug 27, 2026
|
Important Visual changes need review - Review now🟢 UI Tests: n8n: 2 visual and accessibility changes accepted as baselines |
Contributor
Instance AI Workflow EvalImportant This eval does not re-run on new commits. To test your latest push, re-run it against the PR head: gh workflow run ci-instance-ai-evals.yml -f pr=37244…or use the Run workflow button and set pr = Tip 🟢 All 25 units green over 3 runs; 1 flaky — see Failures below. Gate: pass@k = 100% (every unit passes at least once across k runs) — 98.7% pass (74/75 trials over 25 units · k=3) pass@3 100.0% · pass^3 97.2% · LangSmith experiment Failures (1)
Per-test-case results (8)
Workflow checksScored over 24 successful build(s). N/A = check did not apply to that workflow. Error = check could not be measured (e.g. judge timeout).
All workflow checks (2 failing of 35 checks)
|
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
20 participants
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.
Automated
master→3.xsync hit a conflict.Warning
A previous PR for this recurring conflict (#37210, #37079, #36786) was closed without being merged. Closing resolves nothing — the conflict comes back on the next sync. Merge, don't close.
3.xwas not touched. This branch ismastermerged into3.xwith the conflict markers committed, so you can see exactly what clashed. The required checks stay red until they are resolved, so this PR cannot be merged half-done.How to resolve
git fetch origin sync/master-to-3x && git switch sync/master-to-3xgit push origin sync/master-to-3xmaster's commits come in as-is and your fix stays its own commit — nothing is squashed. Never close this PR unmerged: closing resolves nothing and the same conflict reopens on the next sync.Daily syncs are paused until this PR is merged. The next sync then replays
3.xonto master linearly again — which also drops this merge commit and its markers out of3.x's history — and verifies the result is exactly what a merge would produce.Conflicted files
.code-health-baseline.jsonpackages/@n8n/nodes-langchain/nodes/agents/Agent/agents/ConversationalAgent/execute.tspackages/@n8n/nodes-langchain/nodes/agents/Agent/agents/ReActAgent/execute.tspackages/@n8n/nodes-langchain/nodes/vector_store/VectorStoreSupabaseInsert/VectorStoreSupabaseInsert.node.tspackages/@n8n/nodes-langchain/nodes/vector_store/VectorStoreSupabaseLoad/VectorStoreSupabaseLoad.node.tsAuto-resolved for you
These tool-generated files also conflicted and were resolved mechanically — no action needed:
pnpm-lock.yamlLikely owners
Authors of the 3.x commits behind the conflicted files, requested as reviewers: