chore(deps): update ghcr.io/settlemint/codestudio-asset-tokenization-kit docker tag to v2.0.0-main.141891

[renovate]

This PR contains the following updates:

Package	Update	Change	OpenSSF
ghcr.io/settlemint/codestudio-asset-tokenization-kit	patch	2.0.0-main.141841 -> 2.0.0-main.141891

---

Configuration

📅 Schedule: Branch creation - At 12:00 AM through 04:59 AM and 10:00 PM through 11:59 PM, Monday through Friday ( * 0-4,22-23 * * 1-5 ), Only on Sunday and Saturday ( * * * * 0,6 ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.

---

Summary by cubic

Updated the docker-compose to use ghcr.io/settlemint/codestudio-asset-tokenization-kit:2.0.0-main.141891 for the asset-tokenization-kit-content service. Keeps the dependency current.

^{Written for commit 4d91649. Summary will update automatically on new commits.}

[cubic-dev-ai]

No issues found across 1 file

[sentry]

Bug: Race condition in QA workflow causes silent documentation build failures due to detached docker-compose.
_{Severity: MEDIUM | Confidence: Medium}

🔍 Detailed Analysis

The GitHub QA workflow launches a docker-compose service in detached mode (-d) to generate documentation. It does not wait for the container to complete its operations, nor does it check the exit status of the docker-compose command. Immediately after, bun run build executes, which includes next build. If the updated Docker image (version 141891) introduces breaking changes that cause the documentation generation within the container to fail (e.g., cp command fails), the workflow proceeds unaware. This creates a race condition where next build may run before documentation files are copied, leading to a successful build but with missing or incomplete documentation for the asset-tokenization-kit.

💡 Suggested Fix

Modify the GitHub QA workflow to wait for the docker-compose service to complete and check its exit status before proceeding with bun run build. Consider using docker compose up --wait or similar mechanisms.

🤖 Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: docker-compose.yml#L4

Potential issue: The GitHub QA workflow launches a `docker-compose` service in detached
mode (`-d`) to generate documentation. It does not wait for the container to complete
its operations, nor does it check the exit status of the `docker-compose` command.
Immediately after, `bun run build` executes, which includes `next build`. If the updated
Docker image (version 141891) introduces breaking changes that cause the documentation
generation within the container to fail (e.g., `cp` command fails), the workflow
proceeds unaware. This creates a race condition where `next build` may run before
documentation files are copied, leading to a successful build but with missing or
incomplete documentation for the asset-tokenization-kit.

_{Did we get this right? 👍 / 👎 to inform future reviews.
Reference ID: 4353236}