docs(changelog): cut v0.4.0

[bilby91]

Cuts v0.4.0 by documenting everything merged since v0.3.0.

Highlights

• Added — Podman backend + checkpoint/restore (CheckpointRuntime, project-level C/R) (runtime: checkpoint/restore (CheckpointRuntime) + Podman backend #98)
• Fixed — compose feature security metadata + entrypoint chaining (docker-in-docker now works on compose) (compose: apply feature security metadata + entrypoint chaining to services #103)
• Fixed — orchestrator-driven health probing on Podman + multi-service C/R (Podman: fix compose-devcontainer health + multi-service checkpoint/restore #102)
• Changed — deps bump (deps: Bump github.com/google/go-containerregistry from 0.21.6 to 0.21.7 #101); prebuild dev-environment / CI tooling (devcontainer: add prebuild-based dev environment + CI #88–ci(devcontainer): immutable :sha tag + prune stale build intermediates #93)

After this merges, the release is tagged v0.4.0 (compare links already point there). No code changes — CHANGELOG only.

Follow-ups noted: image-source entrypoint chaining + overrideCommand gating (#104).

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@bilby91, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 28 minutes and 25 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 47046db6-822b-4a07-ab81-e696aa72aa97

📥 Commits

Reviewing files that changed from the base of the PR and between 60eef9e and 237ed5a.

📒 Files selected for processing (1)

• CHANGELOG.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/v0.4.0

---

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