chore: update marimo version

[jpopesculian]

Summary by CodeRabbit

• Chores
  • Updated base Docker image version to 0.1.8 for enhanced stability and performance.
  • Updated default Marimo version to 0.19.2 for improved compatibility and features.

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

[coderabbitai]

📝 Walkthrough

Walkthrough

Two version updates: Docker base image tag changed from main to 0.1.8 in the Dockerfile, and default Marimo version bumped from 0.18.4 to 0.19.2 in the template source file.

Changes

Cohort / File(s)	Summary
Docker Configuration docker/Dockerfile.kubimo	Base image tag pinned to specific version 0.1.8 instead of main
Template Version Defaults template/src/dataset_marimo.rs	Default Marimo version incremented from 0.18.4 to 0.19.2

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A hop, a skip, through versions we go,
From main to 0.1.8, steady and slow,
Marimo's up to 0.19 with glee,
These bumps keep the code fresh as can be! 🌟

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The PR title mentions updating marimo version, but the changeset also includes updating the Docker base image tag from 'main' to '0.1.8', which is a separate and equally significant change not reflected in the title.	Consider revising the title to reflect both changes, such as 'chore: update marimo version and docker base image' or clarify if one change is incidental to the primary objective.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
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 docstrings

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7af24e4 and 0294ffb.

📒 Files selected for processing (2)

• docker/Dockerfile.kubimo
• template/src/dataset_marimo.rs

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (13)

• GitHub Check: linux (x86_64)
• GitHub Check: Test WASM (firefox)
• GitHub Check: linux (x86)
• GitHub Check: Test Workspace
• GitHub Check: Build and publish npm package
• GitHub Check: Test WASM (safari)
• GitHub Check: Check WASM
• GitHub Check: Test WASM (chrome)
• GitHub Check: linux (aarch64)
• GitHub Check: windows (x86)
• GitHub Check: windows (x64)
• GitHub Check: macos (x86_64)
• GitHub Check: macos (aarch64)

🔇 Additional comments (3)

docker/Dockerfile.kubimo (2)

1-1: Good: Pinning the build stage to a specific version improves reproducibility.

Moving from main to 0.1.8 for the build stage is a good practice for build stability.

---

20-20: Inconsistent base image tags between build and runtime stages.

The build stage (line 1) now uses the pinned version 0.1.8, but the runtime stage still uses the mutable main tag. This inconsistency could lead to:

• Non-reproducible deployments when the main tag is updated
• Potential version mismatches between build-time and runtime dependencies

Was keeping main for the runtime stage intentional, or should this also be pinned to 0.1.8 (or another specific version)?

template/src/dataset_marimo.rs (1)

11-11: Version bump is valid.

The update to 0.19.2 is a legitimate, recently released version of marimo (Jan 11, 2026) and integrates cleanly with the existing semver validation logic.

---

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.}