Announcing n8n version 2.0 - coming soon!

[nebulon]

In most cases we will update with upstream unless it is like a whole rewrite of the app (like invoice ninja had for example), in which case we will treat it as some entirely different app.

[umnz]

Do any of the staff use n8n on a daily basis? There are quite a few architectural (and breaking) changes being introduced with 2.0. It's definitely going to need to be tested heavily before deployment. Which raises a good question, if someone has auto update enabled in Cloudron, will 2.0 be automatically deployed or will it require manually updating via Cloudron? Could wake up to a lot of unhappy customers.

[austin]

I wonder when we can see v2

[humptydumpty]

@umnz in the past with other apps that had a breaking or major update, the staff made it that a manual update would be required so it’s safe to assume that would also be the case for n8n v2.0.

[nebulon]

Currently v2 is in our ci pipeline. But as you all mentioned here, it has various breaking changes, so we will take that slowly and yes at least it will be a major package version update, so will require manual intervention to update.

[svtx]

@humptydumpty It's probably a good idea to install a second instance for v2 and import one's flows there for testing before doing an upgrade.

[umnz]

I don't think I've changed much if any of our stock cloudron-n8n instances, and here's what our migration report is saying about upgrading to v2.

Does anyone else want to share theirs? You can find it under Settings > Migration Report > Instance Tab

[firmansi]

Is there any update regarding to this major next update?I see in Cloudron git the update is already started but remain on hold

[joseph]

@firmansi https://git.cloudron.io/packages/n8n-app/-/merge_requests/126 . The tests are being fixed. Should be ready in the coming days.

[DualOSWinWiz]

said in Announcing n8n version 2.0 - coming soon!:

Will be closely watching

Today I did the thing my gut specifically told me not to do: I upgraded n8n → 2.0 on production day.

4 Cloudron instances. 150+ workflows. The kind of numbers that usually trigger the “maybe next weekend…” reflex.

I went in fully expecting chaos, alarms, and at least one mysterious workflow deciding to reinvent itself… and somehow… everything upgraded smoothly. No drama. No broken executions. Not even a passive-aggressive warning.

So yeah—either n8n 2.0 is solid, or the production gods accepted my offering of stress and coffee.

[firmansi]

I already upgraded n8n to the latest version, it went smooth and no significant issues, but one feature that i look for n8n chat hub dont appear in this upgrade,anyone experience differently than mine?