chore: upgrade atlas docker image to canary v1.1.7

[jiparis]

Upgrades the Atlas Docker image used for running database migrations from stable v1.1.6 to canary v1.1.7-0f00ade-canary (digest sha256:cbeb45f5342e8e614a60a7ffa355973e5c45f8a8529651c36b9a8ec7e9337d02).

Only Dockerfile.migrations is updated; common.mk and the CI test workflow retain v1.1.6 since the release is not yet done..

[cubic-dev-ai]

2 issues found across 1 file

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="app/controlplane/Dockerfile.migrations">

<violation number="1" location="app/controlplane/Dockerfile.migrations:3">
P2: The `from:` annotation should record the concrete Atlas tag, not `latest`. Using a mutable tag here breaks the traceability of the pinned digest and can mislead future updates or manual verification.</violation>

<violation number="2" location="app/controlplane/Dockerfile.migrations:6">
P1: Keep the deployment Atlas version aligned with `common.mk` and CI. Right now migrations are validated with `v1.1.6` but deployed with a `v1.1.7` canary, so Atlas-specific behavior can fail only in production.

(Based on your team's feedback about cross-component and version compatibility.) [FEEDBACK_USED]</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}