chore(scaffold): bump marimo to 0.23.14 - #77
Merged
Conversation
Bumps the bundled minimal_workspace marimo 0.23.13 -> 0.23.14 and moves the onboarding notebook's session snapshot metadata.marimo_version in lockstep, so test_snapshot_marimo_version_matches_lock stays green and the pre-built cell outputs replay on deploy (a mismatch would silently fall back to a live kernel run). Session-cache format is unchanged (version "1"). Added an [Unreleased] CHANGELOG entry. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bumps the bundled
minimal_workspacemarimo0.23.13 → 0.23.14. Split out from the general lockfile refresh (#78) because bumping marimo requires the coupled onboarding-notebook session snapshot to move in lockstep.Changes
scaffolds/minimal_workspace/uv.lock—marimo0.23.13 → 0.23.14 (viauv lock --upgrade-package marimo; no other packages move).notebooks/onboarding_success/__marimo__/session/onboarding_success.py.json—metadata.marimo_versionbumped to 0.23.14 so the pre-built session cache still replays on deploy.tests/test_notebook.py::test_snapshot_marimo_version_matches_lockasserts this equals the locked marimo version; a mismatch would silently fall back to a live kernel run. Session-cache format is unchanged (version: "1").[Unreleased] → Changedentry.Tests
make scaffold-lock-checkpasses.test_snapshot_marimo_version_matches_lockpasses (snapshot 0.23.14 == locked 0.23.14).🤖 Generated with Claude Code