chore(deps): update downloads.unstructured.io/unstructured-io/unstructured-api docker tag to v0.1.5

[renovate-bot-cbcoutinho]

This PR contains the following updates:

Package	Update	Change
downloads.unstructured.io/unstructured-io/unstructured-api (source)	patch	0.1.2 → 0.1.5

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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 has been generated by Mend Renovate.

[claude]

PR Review: Dependency Update — unstructured-api 0.1.2 → 0.1.3

This is a Renovate-generated patch version bump for the unstructured-api Docker image used in the development/test environment.

Change: Single-line update in docker-compose.yml — tag 0.1.2 → 0.1.3 with updated SHA digest.

Assessment: Safe to merge

Positive observations:

• SHA digest pinning is maintained (@sha256:...) — this is a security best practice that ensures the exact image is pulled, preventing tag mutation attacks.
• Patch version — low risk, typically contains bug fixes only.
• Scope is narrow — only affects the unstructured service used in the local Docker Compose environment (not a runtime production dependency).

No concerns with code quality, security, or test coverage — no logic changes were made.

Recommendation: Routine maintenance update. Verify CI passes (particularly any tests exercising the unstructured service) and merge when green.

[claude]

PR Review: unstructured-api 0.1.2 to 0.1.5 patch update.

Positive: SHA256 digest is correctly updated alongside the tag (prevents silent image substitution). The unstructured service is profile-gated and integration tests require ENABLE_UNSTRUCTURED=true, so default CI is unaffected. Three patch versions suggests accumulated bug fixes.

Consideration: No changelog linked. Worth a quick check of unstructured-api releases for any behavioral changes (element types, text extraction quality, API response shape) between 0.1.2 and 0.1.5 before merging. If the unstructured profile runs in CI, tests/integration/test_unstructured_api.py is the right validation gate.

Verdict: Safe to merge. Minimal change, digest properly pinned, low-risk patch update.