chore(deps): update prom/prometheus docker tag to v2.54.0

[renovate]

This PR contains the following updates:

Package	Update	Change
prom/prometheus	minor	v2.53.1 -> v2.54.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, 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.

[coderabbitai]

Walkthrough

The recent changes involve an upgrade of the Prometheus Docker image across multiple Docker Compose configuration files. The version has been updated from v2.53.1 to v2.54.0, which may introduce bug fixes, performance enhancements, and new features. The overall structure and functionality of the configurations remain unchanged, ensuring a seamless transition to the newer version.

Changes

Files	Change Summary
.../docker-compose.yml	Updated Prometheus image from v2.53.1 to v2.54.0.
.../docker-compose-monitoring.yml	Updated Prometheus image from v2.53.1 to v2.54.0.

Poem

In the garden of code, where the rabbits hop,
Prometheus blooms, and the updates don’t stop.
With a leap and a bound, we embrace the new,
Version 2.54, oh what joy it brings too!
Bugs dashed away, performance takes flight,
Hooray for our changes, all feels just right! 🐇✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between ebb7ec1 and c656867.

Files selected for processing (4)

• boot-grafana-lgtm/docker/docker-compose.yml (1 hunks)
• boot-strategy-plugin/docker-compose.yml (1 hunks)
• graphql/boot-graphql-webmvc/docker/docker-compose-monitoring.yml (1 hunks)
• jpa/boot-data-envers/docker/docker-compose-monitoring.yml (1 hunks)

Files skipped from review due to trivial changes (2)

• graphql/boot-graphql-webmvc/docker/docker-compose-monitoring.yml
• jpa/boot-data-envers/docker/docker-compose-monitoring.yml

Additional comments not posted (2)

boot-grafana-lgtm/docker/docker-compose.yml (1)

16-16: Prometheus Docker image version update approved.

The update from v2.53.1 to v2.54.0 is straightforward and should include improvements and bug fixes. Ensure that any new features or changes in behavior are compatible with your setup.

boot-strategy-plugin/docker-compose.yml (1)

30-30: Prometheus Docker image version update approved.

The update from v2.53.1 to v2.54.0 is straightforward and should include improvements and bug fixes. Ensure that any new features or changes in behavior are compatible with your setup.