N8N-13 Add workflow to automate n8n updates #144
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request will add a workflow that nearly automates the update of n8n.
Whenever a pull request titled "chore: bump n8n from ..." has been
opened,
this workflow will be executed. It will determine which Node.js version the target n8n uses within its docker image and update thedevcontainer.json
accordingly. It will update the@types/node
dependency to match the requested Node.js version as closely as possible. It will update the n8n child dependenciesn8n-nodes-base
and n8n-workflow in the root dependencies and the custom n8n nodes as well.The only thing which needs to be done manually, is the GitHub workflows, as there is no possibility to grant the right to write to
workflows
using the GitHub token provided by the automation. To simplify this, the workflow will request changes to the pull request and add a comment with all workflow files where the Node.js version does not match the requested one.