chore: Update Chainguard base images

[son-oz]

Summary

Cargo.lock was updated by Clippy.

Testing Process

Checklist

• Add a reference to related issues in the PR description.
• Add unit tests if applicable.
• Add integration tests if applicable.
• Add property-based tests if applicable.
• Update documentation if applicable.

Note

If you are using Monitor in your stack, consider adding your team or organization to our list of Monitor Users in the Wild!

Summary by CodeRabbit

• Chores
  • Updated base Docker images for development and production environments to latest available versions.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Two Dockerfile configurations updated: base image references changed from specific sha256 digests to latest-dev and latest tag variants. Build steps and functionality remain unchanged. No alterations to exported declarations or control flow.

Changes

Cohort / File(s)	Summary
Docker Base Image Updates Dockerfile.development, Dockerfile.production	Base image references updated from digest pins to latest tags: Rust image pinned to latest-dev, Wolfi base pinned to latest. No functional changes to build steps or runtime behavior.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Poem

🐰 "Base images bouncing to latest and greatest,
No more digest chains, just tags that are latest!
Docker dreams dancing with cleaner, fresher views,
Building with bounds—yet the newest of news! 🏗️✨"

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is incomplete and contains inaccurate information. The Summary section states 'Cargo.lock was updated by Clippy' which contradicts the actual changes (Dockerfile updates), and the Testing Process section is empty with no details provided.	Update the Summary to accurately describe the Dockerfile base image updates and clarify the Cargo.lock relationship. Complete the Testing Process section with details about how the image changes were validated.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: updating Chainguard base images from specific digests to latest-dev/latest tags across both Dockerfiles.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch update-chainguard-base-images

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}