Updated N8N but no new Merge node

ria · July 17, 2024, 2:44pm

hi guys, release just went out with 1.51.0

github.com/n8n-io/n8n

fix(core): Ensure correct `Cache-Control` header on `/` as well (no-changelog) (#9983)

master ← fix-cache-control

opened 03:16PM - 09 Jul 24 UTC

netroy

+2 -1

## Summary `express.static` handles `/` automatically, and returns `index.html`…. Setting `index: false` in cache options doesn't solve this unfortunately. So, to ensure that `/` gets the same `Cache-Control` header as any other UI route, we need to move the `historyApiHandler` middleware before any `express.static` handler. ## Review / Merge checklist - [x] PR title and summary are descriptive

github.com/n8n-io/n8n

fix(core): Use Custom cache-control headers force cache-revalidation on `/types/*.json` (no-changelog) (#9981)

master ← less-aggressive-caching-on-types

opened 02:28PM - 09 Jul 24 UTC

netroy

+9 -1

## Summary Since `/types/*.json` does not contain any cache-busting string in t…he url, and since these files can change quite a bit between releases, they should not be as aggressively cached as other static assets. ## Review / Merge checklist - [x] PR title and summary are descriptive

Topic		Replies	Views
Merge node typeVersion 3 is not working properly Questions data-transformation	2	136	August 25, 2024
Same node but different options between two identical installations Questions n8n-node	6	288	July 23, 2024
Merge Node Behavior Change? Questions core , node , merge	4	171	February 26, 2025
Merge with no inputs? Questions workflow-building	5	281	June 24, 2025
New Merge-Nodes Logic - not working for me like the old one did Questions merge	1	384	December 28, 2022

Updated N8N but no new Merge node

Related topics