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

[renovate]

This PR contains the following updates:

Package	Update	Change
lobehub/lobe-chat	patch	v1.49.8 -> v1.49.12

---

Warning

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

---

Release Notes

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

v1.49.12

Compare Source

Version 1.49.12

^{Released on 2025-02-02}

🐛 Bug Fixes

• misc: Fix can not stop generating.

Improvements and Fixes

What's fixed

• misc: Fix can not stop generating, closes #​5671 (ae39c35)

v1.49.9

Compare Source

Version 1.49.9

^{Released on 2025-02-01}

💄 Styles

• misc: Update siliconcloud models.

Improvements and Fixes

Styles

• misc: Update siliconcloud models, closes #​5647 (4b41ad4)

---

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]

The code difference does not contain any irregularities, potential issues, or optimization suggestions based on my analysis. The only change is from v1.49.8 to v1.49.12, which indicates an update of the service's Docker image version. This could be due to bug fixes, new features, performance improvements, or security updates, but without further context about what this deployment is intended for, I can't make assumptions about why this update was necessary beyond that they have been made available. If you need more specific recommendations based on application requirements or other criteria, those would require additional information.