Upgrade Path

n8n 0.66.0 → 0.67.0

1 version, 1 with breaking changes, 0 required stops

Version by version, oldest first

0.67.0 2020-05-12

Breaking

What changed?

The names of the following nodes were not set correctly and got fixed:

  • AMQP Sender
  • Bitbucket-Trigger
  • Coda
  • Eventbrite-Trigger
  • Flow
  • Flow-Trigger
  • Gumroad-Trigger
  • Jira
  • Mailchimp-Trigger
  • PayPal Trigger
  • Read PDF
  • Rocketchat
  • Shopify
  • Shopify-Trigger
  • Stripe-Trigger
  • Toggl-Trigger

When is action necessary?

If any of the nodes mentioned above, are used in any of your workflows.

How to upgrade:

For the nodes mentioned above, you'll need to give them access to the credentials again by opening the credentials and moving them from "No Access" to "Access". After you've done that, there are two ways to upgrade the workflows and to make them work in the new version:

Simple

  • Note down the settings of the nodes before upgrading
  • After upgrading, delete the nodes mentioned above from your workflow, and recreate them

Advanced

After upgrading, select the whole workflow in the editor, copy it, and paste it into a text editor. In the JSON, change the node types manually by replacing the values for "type" as follows:

  • "n8n-nodes-base.amqpSender" -> "n8n-nodes-base.amqp"
  • "n8n-nodes-base.bitbucket" -> "n8n-nodes-base.bitbucketTrigger"
  • "n8n-nodes-base.Coda" -> "n8n-nodes-base.coda"
  • "n8n-nodes-base.eventbrite" -> "n8n-nodes-base.eventbriteTrigger"
  • "n8n-nodes-base.Flow" -> "n8n-nodes-base.flow"
  • "n8n-nodes-base.flow" -> "n8n-nodes-base.flowTrigger"
  • "n8n-nodes-base.gumroad" -> "n8n-nodes-base.gumroadTrigger"
  • "n8n-nodes-base.Jira Software Cloud" -> "n8n-nodes-base.jira"
  • "n8n-nodes-base.Mailchimp" -> "n8n-nodes-base.mailchimpTrigger"
  • "n8n-nodes-base.PayPal" -> "n8n-nodes-base.payPalTrigger"
  • "n8n-nodes-base.Read PDF" -> "n8n-nodes-base.readPDF"
  • "n8n-nodes-base.Rocketchat" -> "n8n-nodes-base.rocketchat"
  • "n8n-nodes-base.shopify" -> "n8n-nodes-base.shopifyTrigger"
  • "n8n-nodes-base.shopifyNode" -> "n8n-nodes-base.shopify"
  • "n8n-nodes-base.stripe" -> "n8n-nodes-base.stripeTrigger"
  • "n8n-nodes-base.toggl" -> "n8n-nodes-base.togglTrigger"

Then delete all existing nodes, and then paste the changed JSON directly into n8n. It should then recreate all the nodes and connections again, this time with working nodes.

From github.com/n8n-io/n8n/blob/master/packages/cli/BREAKING-CHANGES.md

Full release notes for 0.67.0

Release notes from github.com/n8n-io/n8n/releases, and packages/cli/BREAKING-CHANGES.md, and CHANGELOG.md, checked 17 hours ago. Only text the vendor marks as breaking, or puts in a warning/caution/important note, is shown; read the full notes for anything else. n8n keeps its breaking changes in packages/cli/BREAKING-CHANGES.md, one section per version (“What changed?”, “When is action necessary?”); each section is quoted whole as “Breaking” on its version. The “BREAKING CHANGES” sections of CHANGELOG.md (0.198.0, 1.0.0, 1.27.0) are quoted too, and each section of the docs page “n8n 2.0 breaking changes” is quoted as “Upgrade guide” on 2.0.0. GitHub release notes are commit lists and are not quoted. Versions come from npm (package n8n). No required stop is recorded: neither file nor the 2.0 page names a version to install first.