Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 18, 2025

This PR contains the following updates:

Package Change Age Confidence
jupytext 1.17.3 -> 1.18.1 age confidence

Release Notes

mwouts/jupytext (jupytext)

v1.18.1

Compare Source

Fixed

  • Fixed test test_check_source_is_newer_when_using_jupytext_sync to work reliably on systems with low filesystem timestamp resolution (#​1460)

Changed

  • We now use pixi to maintain the local Python environments used for developing and testing Jupytext.

v1.18.0

Compare Source

Added

  • The documentation has a chapter on the Jupytext Sync extension for VS Code (#​1395)
  • We have added a new option --check-source-is-newer to the Jupytext CLI. Use this option if you want to make sure that the file passed as argument to Jupytext is the newest of all paired files, and/or newer than the destination file.
  • We have added a section on Jupyter Collaboration which also provides a very useful autoreload functionality (#​406, #​1401)
  • Pairing groups allow you to define different pairing configurations for specific subsets of notebooks. The formats configuration option now supports a list of format dictionaries for first-match pairing. Use [[formats]] sections in your TOML configuration to define multiple format specifications, where the first matching format is used. This allows applying different pairing rules to notebooks in different locations, such as generating documentation markdown files only for tutorial notebooks (#​1383)
  • We have added more tests to document the complex pairing formats, which also work on Windows (#​1028)
  • Pairing into nested folders was fixed on Windows (#​1028)
  • Jupytext is now tested with Python 3.14 (#​1456)

Fixed

  • The Jupytext CLI now detects if a file it has read or consulted has been modified while it was processing it. That can happen in the context of the Jupytext Sync extension for VS Code (#​1411, vscode-jupytext-sync-#​12). When such a synchronous modification is detected, Jupytext now raises an error. Many thanks to Anne Archibald for reporting the issue and preparing an inspiring PR (#​1417).
  • We don't import notebook when jupyter_server is available (#​1436)
  • Jupytext now supports more characters in the cell metadata keys, to improve compatibility with jupyterlab-slideshow (#​1441). Thanks to Nicolas Thierry for this fix.
  • The function find_jupytext_configuration_file now works with relative directories (#​1440). This fix was contributed by Thierry Parmentelat.
  • We have fixed a parsing error for R Markdown files (#​1429)
  • We have fixed a parsing error when the first cell of the notebook contains a YAML header that is not a dict (#​1444)

Changed


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@codecov
Copy link

codecov bot commented Oct 18, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@renovate renovate bot force-pushed the renovate/jupytext-1.x-lockfile branch from 6900f08 to 24de897 Compare October 19, 2025 16:39
@renovate renovate bot changed the title chore(deps): update dependency jupytext to v1.18.0 chore(deps): update dependency jupytext to v1.18.1 Oct 19, 2025
@sonarqubecloud
Copy link

@wislertt wislertt merged commit 0028a9e into main Oct 20, 2025
13 checks passed
@wislertt wislertt deleted the renovate/jupytext-1.x-lockfile branch October 20, 2025 01:46
@github-actions
Copy link

🎉 This PR is included in version 0.36.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants