Skip to content

chore(deps): update rabbitmq docker tag to v4.1.1 #4073

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 rabbitmq docker tag to v4.1.1 #4073

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
e2537c5
chore(deps): update rabbitmq docker tag to v4.1.1
renovate[bot] Jun 5, 2025
749f7b8
Update app version [skip ci]
Jun 5, 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 ...rabbitmq/4.1.0-management-alpine/data.yml → ...rabbitmq/4.1.1-management-alpine/data.yml
View file
Open in desktop
File renamed without changes.
2 changes: 1 addition & 1 deletion ....1.0-management-alpine/docker-compose.yml → ....1.1-management-alpine/docker-compose.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
services:
rabbitmq:
image: rabbitmq:4.1.0-management-alpine
image: rabbitmq:4.1.1-management-alpine
hostname: rabbitmq
container_name: ${CONTAINER_NAME}
restart: always
Copy link
Member

@wanghe-fit2cloud wanghe-fit2cloud Jun 5, 2025

Choose a reason for hiding this comment

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

The only change here is an update from rabbitmq:4.1.0-management-alpine to rabbitmq:4.1.1-management-alpine. This means that you will be pulling a newer version of the RabbitMQ container with additional management features available in this new version.

Optimization Suggestion: If there are no specific performance or feature requirements that require using the updated version, consider sticking with the existing minor patch version (4.1.0) unless there's a compelling reason to upgrade.

Expand Down