Latest-version in docker-compose.yml for backend, eai, aenderungsserv…

[udobrmuc]

…ice, frontend and online

Pull Request

Changes

• ...
• ...

Reference

Issue: #XXX

Checklist

Note: If some checklist items are not relevant for your PR, just remove them.

General

• Added meaningful PR title and list of changes in the description

Summary by CodeRabbit

• Chores
  • Updated service images to new versions for backend, frontend, and related components to ensure the latest updates are deployed.

[coderabbitai]

"""

Walkthrough

The Docker Compose configuration was updated to replace the SHA256 digests in the image references for backend, frontend, online, eai, and aenderungsservice services with new SHA256 digests, removing the "latest" tag. No other service configurations or settings were modified.

Changes

File(s)	Change Summary
stack/docker-compose.yml	Updated SHA256 digests for backend, frontend, online, eai, and aenderungsservice images; removed "latest" tags.

Poem

🐇
New digests hop into place,
Images tagged with fresh embrace.
Hashes changed, the tags now clear,
Docker pulls without a fear.
A rabbit’s cheer for stacks refined,
Smooth and swift, all well aligned!

"""

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 608637f and 13d3fc1.

📒 Files selected for processing (1)

• stack/docker-compose.yml (5 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: build (ehrenamt-justiz-backend)

🔇 Additional comments (1)

stack/docker-compose.yml (1)

153-153: 👍 Digest-only image references restore deterministic builds

Removing the mutable :latest tag and keeping the SHA-256 digest achieves reproducible pulls and satisfies previous supply-chain feedback. Spacing is also YAML-lint–clean now.

Also applies to: 172-172, 185-185, 200-200, 222-222

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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>, please review it.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 using 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 generate sequence diagram to generate a sequence diagram of the changes in this 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.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

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.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1f6c021 and fd53671.

📒 Files selected for processing (1)

• stack/docker-compose.yml (5 hunks)

🧰 Additional context used

🪛 YAMLlint (1.37.1)

stack/docker-compose.yml

[error] 153-153: too many spaces after colon

(colons)

---

[error] 172-172: too many spaces after colon

(colons)

---

[error] 185-185: too many spaces after colon

(colons)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: build (ehrenamt-justiz-backend)

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 47ea251 and 608637f.

📒 Files selected for processing (1)

• stack/docker-compose.yml (5 hunks)