Skip to content

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

Merged
wanghe-fit2cloud merged 2 commits into
devfrom
renovate/lobehub-lobe-chat-1.x
Apr 13, 2025
Merged

chore(deps): update lobehub/lobe-chat docker tag to v1.79.5#3662
wanghe-fit2cloud merged 2 commits into
devfrom
renovate/lobehub-lobe-chat-1.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Apr 10, 2025

This PR contains the following updates:

Package Update Change
lobehub/lobe-chat patch 1.79.4 -> 1.79.5

Warning

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


Release Notes

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

v1.79.5

Compare Source

Released on 2025-04-10

🐛 Bug Fixes
  • misc: Fix langfuse intergation.

Improvements and Fixes
What's fixed


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
Copy link
Copy Markdown

f2c-ci-robot Bot commented Apr 10, 2025

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
Copy link
Copy Markdown

f2c-ci-robot Bot commented Apr 10, 2025

[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:

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

image: lobehub/lobe-chat:1.79.5
container_name: ${CONTAINER_NAME}
restart: always
networks:
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The code snippet appears to be updating the version of an LobeChat service from 1.79.4 to 1.79.5. Here's the relevant part:

   lobe-chat:
-    image: lobehub/lobe-chat:1.79.4
+    image: lobehub/lobe-chat:1.79.5

Potential Issues and Optimization Suggestions

Irregularity/Issue:

There are no apparent issues with this particular line update.

Optimizations/Cleanups:

  • Ensure that environment variables like $CONTAINER_NAME are correctly set if they were intended for use here.
  • There is no indication of network settings, so assume the existing configuration remains unchanged.

Conclusion

This update simply changes the specified Docker image used for the lobe-chat service from 1.79.4 to 1.79.5, without introducing any additional dependencies or configurations on either side. If $CONTAINER_NAME was a critical variable, it should be checked before deploying the updated service to ensure it aligns with other deployment environments.

@wanghe-fit2cloud wanghe-fit2cloud merged commit 69b3fa8 into dev Apr 13, 2025
1 check was pending
@wanghe-fit2cloud wanghe-fit2cloud deleted the renovate/lobehub-lobe-chat-1.x branch April 13, 2025 14:46
pull Bot pushed a commit to dreamoeu/appstore that referenced this pull request Nov 15, 2025
…-dozzle-8.x

chore(deps): update amir20/dozzle docker tag to v8.14.8
pull Bot pushed a commit to dreamoeu/appstore that referenced this pull request Apr 11, 2026
…n-openclaw-sandbox-2026.x

Update ghcr.io/okxlin/openclaw-sandbox Docker tag to v2026.4.10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant