Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
for more information, see https://pre-commit.ci
mscolnick
approved these changes
Jan 17, 2026
akshayka
approved these changes
Jan 18, 2026
|
🚀 Development release published. You may be able to view the changes at https://marimo.app?v=0.19.5-dev12 |
botterYosuke
pushed a commit
to botterYosuke/marimo
that referenced
this pull request
Jan 18, 2026
## 📝 Summary
When exporting marimo notebooks to .ipynb format, we now include
marimo-specific metadata at the notebook level. This enables better
round-trip conversion and interoperability.
Export (marimo -> ipynb):
- `metadata.marimo.marimo_version` - the marimo version that generated
the notebook
- `metadata.marimo.app_config` - non-default app configuration (width,
sql_output, etc.)
- `metadata.marimo.header` - PEP 723 inline script metadata, docstrings
- `metadata.language_info` - standard Jupyter language info (without
Python version to avoid environment-dependent snapshots)
Import (ipynb -> marimo):
- Reads m`etadata.marimo.app_config` to restore app configuration
- Reads `metadata.marimo.header` to restore PEP 723 metadata
- Reads cell-level `metadata.marimo.config` to restore hide_code,
column, disabled
### Example output
```json
{
"metadata": {
"marimo": {
"marimo_version": "0.10.0",
"app_config": {
"width": "full",
"sql_output": "native"
},
"header": "# /// script\n# dependencies = [\"pandas\"]\n# ///"
},
"language_info": {
"name": "python",
"codemirror_mode": {"name": "ipython", "version": 3},
// ...
}
}
}
```
## Spec compliance
The Jupyter nbformat schema explicitly allows custom metadata via
`"additionalProperties": true` on the metadata object. Using a
tool-specific namespace key is the canonical approach, as seen with
other tools:
- Google Colab: metadata.colab
- ipypublish: metadata.ipub
- Pretty Jupyter: metadata.pj_metadata
Reference:
https://nbformat.readthedocs.io/en/latest/format_description.html
---------
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
mscolnick
pushed a commit
that referenced
this pull request
Jan 19, 2026
## 📝 Summary
When exporting marimo notebooks to .ipynb format, we now include
marimo-specific metadata at the notebook level. This enables better
round-trip conversion and interoperability.
Export (marimo -> ipynb):
- `metadata.marimo.marimo_version` - the marimo version that generated
the notebook
- `metadata.marimo.app_config` - non-default app configuration (width,
sql_output, etc.)
- `metadata.marimo.header` - PEP 723 inline script metadata, docstrings
- `metadata.language_info` - standard Jupyter language info (without
Python version to avoid environment-dependent snapshots)
Import (ipynb -> marimo):
- Reads m`etadata.marimo.app_config` to restore app configuration
- Reads `metadata.marimo.header` to restore PEP 723 metadata
- Reads cell-level `metadata.marimo.config` to restore hide_code,
column, disabled
### Example output
```json
{
"metadata": {
"marimo": {
"marimo_version": "0.10.0",
"app_config": {
"width": "full",
"sql_output": "native"
},
"header": "# /// script\n# dependencies = [\"pandas\"]\n# ///"
},
"language_info": {
"name": "python",
"codemirror_mode": {"name": "ipython", "version": 3},
// ...
}
}
}
```
## Spec compliance
The Jupyter nbformat schema explicitly allows custom metadata via
`"additionalProperties": true` on the metadata object. Using a
tool-specific namespace key is the canonical approach, as seen with
other tools:
- Google Colab: metadata.colab
- ipypublish: metadata.ipub
- Pretty Jupyter: metadata.pj_metadata
Reference:
https://nbformat.readthedocs.io/en/latest/format_description.html
---------
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.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
3 participants
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
When exporting marimo notebooks to .ipynb format, we now include marimo-specific metadata at the notebook level. This enables better round-trip conversion and interoperability.
Export (marimo -> ipynb):
metadata.marimo.marimo_version- the marimo version that generated the notebookmetadata.marimo.app_config- non-default app configuration (width, sql_output, etc.)metadata.marimo.header- PEP 723 inline script metadata, docstringsmetadata.language_info- standard Jupyter language info (without Python version to avoid environment-dependent snapshots)Import (ipynb -> marimo):
etadata.marimo.app_configto restore app configurationmetadata.marimo.headerto restore PEP 723 metadatametadata.marimo.configto restore hide_code, column, disabledExample output
{ "metadata": { "marimo": { "marimo_version": "0.10.0", "app_config": { "width": "full", "sql_output": "native" }, "header": "# /// script\n# dependencies = [\"pandas\"]\n# ///" }, "language_info": { "name": "python", "codemirror_mode": {"name": "ipython", "version": 3}, // ... } } }Spec compliance
The Jupyter nbformat schema explicitly allows custom metadata via
"additionalProperties": trueon the metadata object. Using a tool-specific namespace key is the canonical approach, as seen with other tools:Reference: https://nbformat.readthedocs.io/en/latest/format_description.html