chore(deps): bump Ryuk to v0.14.0

[mdelapenya]

What does this PR do?

Bump Ryuk to v0.14.0, whose image is considerably smaller.

Why is it important?

Reduce pull time and footprint of the ryuk image

Related issues

• Relates to Apply UPX compression with comprehensive benchmarking and GHCR registry testing: 69% size reduction with real egress analysis moby-ryuk#213

[netlify]

✅ Deploy Preview for testcontainers-go ready!

Name	Link
🔨 Latest commit	967f2ba
🔍 Latest deploy log	https://app.netlify.com/projects/testcontainers-go/deploys/691d6b669474850008f659d1
😎 Deploy Preview	https://deploy-preview-3313--testcontainers-go.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Summary by CodeRabbit

• Chores
  • Updated the default Ryuk image from 0.13.0 to 0.14.0.
  • Future runs will automatically pull and use the newer image; existing custom image overrides remain unaffected.
  • No functional behavior changes beyond the version bump.
  • Users may see a one-time image download on first use after upgrading.

Walkthrough

Updates the default Ryuk image version in configuration from 0.13.0 to 0.14.0 by changing the ReaperDefaultImage constant. No other code changes.

Changes

Cohort / File(s)	Summary
Config constant update internal/config/config.go	Bumps ReaperDefaultImage from testcontainers/ryuk:0.13.0 to testcontainers/ryuk:0.14.0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A tweak to the tag on a moonlit night,
Ryuk hops versions—new lantern, same light.
I wiggle my whiskers, configs align,
0.14.0 tastes crisp and fine.
Burrow secured, I thump with cheer—
tiny change, tidy gear!

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title succinctly follows conventional commit style and accurately reflects the primary change by specifying the dependency bump of Ryuk to version v0.14.0, matching the updated constant in the code without any extraneous information.
Description Check	✅ Passed	The description clearly states what the PR does by bumping Ryuk to v0.14.0 and why it is important by noting reduced pull time and footprint, and it also links to the related upstream change, making it directly relevant and sufficiently informative for this dependency update.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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