merge queue: embarking main (80b9271) and [#1944 + #1945] together

[mergify]

🎉 This combination of pull requests has been checked successfully and will be merged soon. 🎉

Branch main (80b9271) and [#1944 + #1945] are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of [#1944 + #1945].
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule Github Actions Updates for merge:

• any of [🛡 GitHub repository ruleset rule main]:
  • check-neutral = Mergify Merge Protections
  • check-skipped = Mergify Merge Protections
  • check-success = Mergify Merge Protections

Required conditions to stay in the queue:

• author = renovate[bot]
  • Update qdrant/qdrant:latest Docker digest to 45f8e3d #1944
  • Update docker/login-action action to v4.2.0 - autoclosed #1945
• any of:
  • files ~= ^.github/workflows
    • Update qdrant/qdrant:latest Docker digest to 45f8e3d #1944
    • Update docker/login-action action to v4.2.0 - autoclosed #1945
  • files ~= action.yaml$
    • Update qdrant/qdrant:latest Docker digest to 45f8e3d #1944
    • Update docker/login-action action to v4.2.0 - autoclosed #1945
• any of [🛡 GitHub repository ruleset rule main]:
  • check-neutral = Mergify Merge Protections
    • Update qdrant/qdrant:latest Docker digest to 45f8e3d #1944
    • Update docker/login-action action to v4.2.0 - autoclosed #1945
  • check-skipped = Mergify Merge Protections
    • Update qdrant/qdrant:latest Docker digest to 45f8e3d #1944
    • Update docker/login-action action to v4.2.0 - autoclosed #1945
  • check-success = Mergify Merge Protections
    • Update qdrant/qdrant:latest Docker digest to 45f8e3d #1944
    • Update docker/login-action action to v4.2.0 - autoclosed #1945

---
checking_base_sha: 80b9271044426f605496ca2549fda9e92ada7af5
previous_failed_batches: []
pull_requests:
  - number: 1944
    scopes: []
  - number: 1945
    scopes: []
scopes: []
...

[semanticdiff-com]

Review changes with  

Changed Files

File	Status
.github/workflows/.docker.yaml	0% smaller
docker-compose-dev.yaml	0% smaller
docker-compose.yaml	0% smaller

[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 SonarQube Cloud

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates CI Docker login action and refreshes the pinned Qdrant image digest across workflows and compose files to align with newer versions while keeping explicit pinning.

File-Level Changes

Change	Details	Files
Bump GitHub Actions docker/login-action used in the CI workflow to the latest v4.2.0 commit.	Update the docker/login-action pinned commit hash from v4.1.0 to the v4.2.0 commit in the Docker-related GitHub Actions workflow job that logs into the container registry	.github/workflows/.docker.yaml
Refresh pinned Qdrant vector database image digest across workflows and compose configurations.	Update the Qdrant container image digest used by the container_health workflow service to a newer sha256 value while staying on the latest tag Update the Qdrant image digest in the development docker-compose file to match the new digest Update the Qdrant image digest in the main docker-compose file to match the new digest	.github/workflows/.docker.yaml docker-compose-dev.yaml docker-compose.yaml

Possibly linked issues

• #0: This PR fulfills the dashboard’s pending updates for qdrant Docker digest and docker/login-action v4.2.0.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.