Render deploy failed ([email protected] error)

Questions
1

Hi all - I’m new to this so please bear with me!

I regularly sync my n8n github, which triggers a deployment in Render. Recently, it failed with this error:

ERROR The following patches were not applied: [email protected], [email protected], [email protected], @types/[email protected], @types/[email protected], @types/[email protected], [email protected], eslint-plugin-n8n-local-rules Either remove them from “patchedDependencies” or update them to match packages in your dependencies.

I was able to find the patch in my github instance.

Unfortunately, I have no clue what to do next as I don’t really understand this too well. I get that I can remove or update, but don’t know what removing will do or how to update it to the correct version.

Can anyone help? Thank you in advance!

2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
3

Try updating n8n that may resolve the patch conflict.

4

Thank you Daniel! I don’t use the cloud hosting from n8n, I use Render.io - I don’t see an option to upgrade my n8n instance and believed I was doing that each time I went to Github and hit “sync fork.” Am I able to update my n8n instance with this setup? I have the “dev” version of n8n.

5

Hi @briangormanh ,
The error occurs because your synced fork has outdated patch references. Since you’re using Render with the dev version:

  1. Update your fork’s package.json to remove the problematic patch entries:
  • Find the “patchedDependencies” section
  • Remove the entries for [email protected] and other failing patches (be very careful and take backups before)
  1. Alternatively, if you haven’t made custom changes, consider restarting with a fresh fork of the current n8n main branch instead of syncing your existing fork.(please, prefer this if you can start from fresh)

These patch conflicts typically happen when syncing across major version changes in the development branch.

6

Thank you so much! I’m interested in just creating a new fork since I haven’t made any custom changes to the github for n8n.

Can I simply create a new fork and then point to that repository URL within Render? In other words, just update that and leave everything else the same in Render?

The only thing I’m so worried about is losing my workflows!

Thank you so much for your guidance.

7

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.