chore(deps): update n8nio/n8n docker tag to v1.88.0

[renovate]

This PR contains the following updates:

Package	Update	Change
n8nio/n8n (source)	minor	1.87.2 -> 1.88.0

---

Warning

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

---

Release Notes

n8n-io/n8n (n8nio/n8n)

v1.88.0

Bug Fixes

• API: Fix ratio tests on insights by workflow (#​14448) (6c73d7e)
• Code Node: Use an explicit indexURL to load the pyodide runtime (#​14487) (860bb1e)
• core: Fall back to regular mode for execute and executeBatch commands (#​14381) (84e85c9)
• core: Fix routing for waiting webhooks and forms (#​14470) (b5d5b57)
• editor: Fix race condition for updating node and workflow execution status (#​14353) (a495d81)
• editor: Improve node creator items typing and fix missing icons (#​14449) (ad6c83a)
• editor: Inline expression previews are not displayed in NDV (#​14475) (aee83bf)
• editor: Prevent moving non owned workflows to folders (#​14474) (2a5c3d4)
• Isolate license SDK proxy settings to avoid affecting unrelated requests (#​14451) (7463f0c)

Features

• Azure Cosmos DB Node: New node (#​14156) (b52f9f0)
• Email Trigger (IMAP) Node: IMAP trigger node returns message UIDs (#​13152) (4578709)
• MCP Client Tool Node: Add MCP Client Tool Node to connect to MCP servers over SSE (#​14464) (34252f5)
• MCP Server Trigger Node: Add MCP Server Trigger node to expose tools to MCP clients (#​14403) (8360283)
• Milvus Vector Store Node: Add support for the Milvus vector db (#​14404) (048b9d7)

Performance Improvements

• core: Batch raw insights save and add metadata cache (#​14261) (60afb46)

---

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.

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/test-infra 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.

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]

There appears to be no noticeable difference between the two versions of the services.homeassistant.image line that you provided. The upgrade from v1.87.2 to v1.88.0 does not introduce significant changes at this level, so there are likely no specific irregularities or issues with this update.

For optimization suggestions, since we're working with Docker images and container configurations, here's some general advice:

1. Performance Considerations:

   • Ensure that the container is running on an appropriate CPU architecture (e.g., amd64 for Linux). This might impact performance if you need special optimizations.

2. Resource Utilization:

   • Review whether you've set a CPU limit (cpu-shares or --cpuset-cpus) or memory limit (memory.limit_in_bytes). Setting these can help manage resource usage effectively.

3. Network Management:

   • Check if your network settings are optimized. You might want to use overlay networks for better performance when multiple services run inside a cluster setup.

4. Environment Variables:

   • If you have any secrets or sensitive information stored in environment variables, ensure they are properly encrypted and managed securely.

Overall, the change seems minimal and aligns well with current practices in using N8N containers. No further actions are recommended without more detailed knowledge about the environment and intended use case.