chore(deps): update lobehub/lobe-chat docker tag to v1.77.17

[renovate]

This PR contains the following updates:

Package	Update	Change
lobehub/lobe-chat	patch	1.77.15 -> 1.77.17

---

Warning

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

---

Release Notes

lobehub/lobe-chat (lobehub/lobe-chat)

v1.77.17

Compare Source

^{Released on 2025-04-08}

🐛 Bug Fixes

• misc: Refactor ollama pull flow and model service.

Improvements and Fixes

What's fixed

• misc: Refactor ollama pull flow and model service, closes #​7330 (44d63b8)

v1.77.16

Compare Source

^{Released on 2025-04-06}

♻ Code Refactoring

• misc: Refactor the file service.

Improvements and Fixes

Code refactoring

• misc: Refactor the file service, closes #​7323 (3721b88)

---

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

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 the image tag has been updated from lobehub/lobe-chat:1.77.15 to lobehub/lobe-chat:1.77.16. This means you should pull the new version of the Docker image before running the application again.

Optimization suggestion would be to remove old tags if they are not needed, keeping your repo clean, which can save storage space and reduce load on repository servers. However, this change does not require immediate attention based solely on the provided diff.

[wanghe-fit2cloud]

The only difference I see is that in the original version, it uses lobehub/lobe-chat:1.77.15, while the modified version uses lobehub/lobe-chat:1.77.17. This indicates that the image tag has been updated from an older version to a newer one.

To ensure consistency and potentially better performance with updates, it's generally recommended to use the latest available images unless there is a specific reason to stay on an older version (always restart policy also seems appropriate). However, if you can't update immediately, this should be noted for future migrations.

No significant issues were found with the rest of the configuration. If you plan on further optimizations or adjustments, please let me know!

[wanghe-fit2cloud]

The provided code snippet contains an error: there is a duplicate image property within the same service block. This could lead to unexpected behavior. To correct this, you should either update the value of the existing image property from "lobehub/lobe-chat:1.77.15" to "lobehub/lobe-chat:1.77.17", remove the second line entirely if "lobehub/lobe-chat:1.77.15" needs no longer be used for this service, or combine both properties into one with different versions.

Here's a corrected version:

services:
  lobe-chat:
    image: lobehub/lobe-chat:1.77.17
    container_name: ${CONTAINER_NAME}
    restart: always
    networks:

Note that the use of ${CONTAINER_NAME} in container_name suggests it might be defined somewhere else in your configuration file. If not, you should replace ${CONTAINER_NAME} with an actual name or comment it out temporarily if necessary until resolved.