-
Potentially the Task Runner separation from the original container could be a BC to the current Cloudron Packaging?
-
J joseph moved this topic from Announcements
-
Will be closely watching
-
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.
-
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.
-
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.
@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.
-
@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.
@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.

