Announcing n8n version 2.0 - coming soon!

[robi]

Announcing n8n version 2.0 - our best n8n ever!

[From the n8n devs]
I’m super excited to share that we’ll soon be releasing n8n version 2.0.0 (v2 for short)

It’s been over two years since we released n8n 1.0.0 back in July 2023. Since then, n8n has made some incredible strides thanks to the feedback and help we’ve received from our amazing community and all of the hard work from our tireless engineering & product teams.

As a result, n8n has proven itself and become the solution of choice for workflow automation & Agentic AI orchestration for millions of individuals and some of the world’s largest companies.

And with version 2.0, n8n is more mature, more secure and more reliable than ever before.

We’re adding some cool new features and making a few necessary breaking changes to lay the groundwork for even better things in the future.

We’re posting about this here in the community first to help you understand what to expect and provide a place to ask questions.

When is this happening?

We will be releasing:

• Version 2.0.0 (beta) in early December, currently scheduled for Dec 8th.

• Version 2.0.x (stable) mid December, currently scheduled for Dec 15th.

Please follow our release notes page for the latest updates: https://docs.n8n.io/release-notes/

What’s new with v2?

We’re launching:

• Autosave - yup, it’s finally here! (will be launched soon after stable is released)

• Improved canvas look and feel

• Updated sidebar

• A few other surprises (coming soon).

We’ll provide more details on the new and updated features soon.

What are the breaking changes?

In order to improve security & performance, simplify configuration, and remove legacy features, we’re making some necessary changes to expected behaviour, security enforcement, storage backends, configuration and environment variables.

We created a dedicated docs page that covers all of these changes and provides migration paths for how to address them: https://docs.n8n.io/2-0-breaking-changes/

We also added a Migration Report tool that shows workflow or instance level issues you need to address before upgrading. The report is available within your n8n instance under Settings → Migration Report and is live since version 1.121.0

Please note: Only global admins will see the Migration Report in their settings.

Does the community version get all of the v2 updates?

Yes. All of the changes we’re making for v2 apply to community, cloud and enterprise/business versions of n8n.

What about version 1.x?

Versions 1.x will continue to be supported and updated for 3 months after the release of 2.x, but will only include bug security fixes. No new features will be added to versions 1.x after the release of 2.x

https://community.n8n.io/t/announcing-n8n-version-2-0-coming-soon/226475

[Divemasterza]

Potentially the Task Runner separation from the original container could be a BC to the current Cloudron Packaging?

[DualOSWinWiz]

Will be closely watching

[sparkwise]

When will this auto-update on Cloudron? We'll all need some time to work through the full list of breaking changes (https://docs.n8n.io/2-0-breaking-changes/) before then.

[nebulon]

We will probably publish that as a major package update, so it will not auto-update and break things without notice.

[umnz]

It looks like they will continue to bug fix v1 while v2 is distributed. How is that going to be handled by the Cloudron updater? Will we be able to stay on v1 with Cloudron if we don't want to or cannot upgrade to v2 but need the v1 patches?

[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