Skip to content

chore(deps): update mongo docker tag to v6.0.24 #4061

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
wanghe-fit2cloud merged 2 commits into from
Jun 5, 2025
Merged

chore(deps): update mongo docker tag to v6.0.24 #4061

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
17f4721
chore(deps): update mongo docker tag to v6.0.24
renovate[bot] Jun 4, 2025
e070c2a
Update app version [skip ci]
Jun 4, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
0 apps/mongodb/6.0.22/data.yml → apps/mongodb/6.0.24/data.yml
View file
Open in desktop
File renamed without changes.
2 changes: 1 addition & 1 deletion apps/mongodb/6.0.22/docker-compose.yml → apps/mongodb/6.0.24/docker-compose.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
services:
mongodb:
container_name: ${CONTAINER_NAME}
image: mongo:6.0.23
image: mongo:6.0.24
restart: always
environment:
MONGO_INITDB_ROOT_USERNAME: ${PANEL_DB_ROOT_USER}
Copy link
Member

@wanghe-fit2cloud wanghe-fit2cloud Jun 4, 2025

Choose a reason for hiding this comment

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

Yes, there is one change between versions 6.0.23 and 6.0.24 of the MongoDB Docker image:

The image line has been updated from "mongo:6.0.23" to "mongo:6.0.24".

This indicates that the latest version of the MongoDB Docker image (version 6.0.24) has been used instead of the older version (version 6.0.23). It's generally recommended to use the most recent stable version available to ensure compatibility with the latest features, security patches, and updates.

No significant issue or opportunity for optimization was identified based on the changes. However, it's good practice to regularly update dependencies such as databases to maintain performance and security improvements.

Expand Down