chore(deps): update n8nio/n8n docker tag to v1.97.0 - autoclosed

[renovate]

This PR contains the following updates:

Package	Update	Change
n8nio/n8n (source)	minor	1.95.2 -> 1.97.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

n8n-io/n8n (n8nio/n8n)

v1.97.0

Bug Fixes

• core: Allow dotfiles in sendFile to fix WorkFlow settings 404 error (#​14744) (7928a9b)
• core: Honor absolute paths for N8N_LOG_FILE_LOCATION (#​15873) (1e5b905)
• core: Normalize trailing slash when setting CORS headers for test webhooks (#​15906) (61d0c6a)

Performance Improvements

• core: Lazyload LDAP during bootup (#​15907) (31b6f32)

v1.96.0

Bug Fixes

• API: Allow false as a dependant value for public api json schema validation (#​15858) (5a8899c)
• Check if form trigger URL is live before oppening pop-up (#​15800) (041ada1)
• core: Don't allow creating more projects than allowed by exploiting a race condition (#​15218) (6466e76)
• core: Fix sorting of executions not working on postgres and mysql (#​15423) (eca282d)
• core: Fix timezone-dependent test failures in Insights weekly compaction (#​15680) (096806a)
• core: Simplify Websocket origin security checks (#​15761) (bbe2b12)
• core: Solve memory leak in TaskRequester (#​15768) (0398505)
• core: Support helpers.request in task runners (#​15859) (7f8b943)
• editor: Deactivate workflow on save if trigger is missing (#​15642) (3ba6419)
• editor: Delete all connections of nodes with multiple ones when removed from canvas (#​15713) (c4ea757)
• editor: Fix Execute workflow button hover state (#​15518) (57d7b5e)
• editor: Handle Insights calculations to prevent Infinity numbers (#​15727) (d1a39d9)
• editor: Move focus to search input in RLC (#​15741) (fee10da)
• editor: Set deterministic width for sidebar (#​15753) (3f9a271)
• editor: Simplifying empty project deletion (#​15834) (6bf2d8a)
• editor: Update copy for debug modal paywall (#​15905) (d0ff662)
• editor: Use last task data for calculating the current state (#​15546) (1daf0ff)
• GitHub Node: Update auth urls for enterprise server (#​15533) (bc66d9f)
• Jina AI Node: Default value for "Output format" option (#​15683) (e125854)
• Microsoft SharePoint Node: Add back the support for cred only node (#​15806) (0fdeba5)
• n8n Form Node: Use execution.mode instead of hard coding webhook (#​15647) (636e9f4)
• Run evaluations loop manually always from first row (#​15794) (b8ab4b6)
• Skip subworkflow input test temporarily (#​15803) (ba70cab)

Features

• API: Add user management endpoints to the Projects Public API (#​12329) (4459c7e)
• core: Allow specifying Content-Security-Policy-Report-Only (#​15805) (c127846)
• core: Start listening to IPv6 addresses as well by default (#​15810) (9f44f40)
• editor: Add ability to extract sub-workflows to canvas context menu (#​15538) (5985df6)
• editor: Combine 'Move to Folder' and 'Change owner' modals (#​15756) (e860dd6)
• editor: Support pasting an expression into a number parameter (#​15722) (2a1475d)
• MCP Server Trigger Node: Cleanup MCP server management, use sanitized trigger node's name as name for the MCP server (#​15751) (07a636e)
• Perplexity Node: New node (#​13604) (6d3e6ee)
• Respond to Webhook Node: Setting to configure outputs (#​15619) (be5f14e)

Performance Improvements

• core: Shorten bootup for all instance types (#​15856) (73c9a52)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[f2c-ci-robot]

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[f2c-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[wanghe-fit2cloud]

The only difference is that n8nio/n8n:1.95.2 has been updated to n8nio/n8n:1.97.0. No other code changes have been made, so there are no issues or optimization suggestions at this time. The version update seems minor but can help with security updates and performance improvements.

[wanghe-fit2cloud]

Your Dockerfile appears to be correctly updating the N8N image from version 1.95.2 to 1.97.0. This update should bring you access to newer features and improvements.

Potential Issues:

• No Changes: There are no apparent changes between the two versions listed, indicating that this change is simply a version upgrade with no other modifications. Ensure there aren't any specific needs or dependencies on additional configurations that require adjustments after upgrading.

Suggestions for Optimization:

1. Security Updates:

   • Check if there are security patches available for any vulnerabilities in the updated version of N8N (version 1.97.0) since your previous version (1.95.2). Updating might include security fixes.

2. Networks Configuration:

   • Ensure all network configurations mentioned in your file continue to work properly. If new environments or container requirements were added, make sure those are adjusted accordingly.

3. Environment Variables:

   • Verify that any environment variables like ${CONTAINER_NAME} have not inadvertently changed from how they were configured initially.

4. Container Restart Policies:

   • It's good to keep consistent settings for restarting containers. The policy used here (always) ensures that the docker-compose service will automatically restart the container even if it stops unexpectedly. However, consider adding logging strategies to help monitor the behavior post-update.

Since the changes seem minimal, ensuring correct configuration for existing services would typically suffice for an update without significant performance impacts.