build(deps): bump jupytext from 1.17.3 to 1.18.1 in the general-dependencies group

[dependabot]

Bumps the general-dependencies group with 1 update: jupytext.

Updates jupytext from 1.17.3 to 1.18.1

Release notes

Sourced from jupytext's releases.

Version 1.18.1

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.

Version 1.18.0

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](caenrigen/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

• We have updated the pre-commit hooks. The code is now formatted using ruff format, and updated for Python 3.9+ using https://github.com/asottile/pyupgrade (#1423)

Version 1.18.0rc0

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 do 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](caenrigen/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 support 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)

Changed

• We have updated the pre-commit hooks. The code is now formatted using ruff format, and updated for Python 3.9+ using https://github.com/asottile/pyupgrade (#1423)

Changelog

Sourced from jupytext's changelog.

1.18.1 (2025-10-19)

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.

1.18.0 (2025-10-18)

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](caenrigen/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

• We have updated the pre-commit hooks. The code is now formatted using ruff format, and updated for Python 3.9+ using https://github.com/asottile/pyupgrade (#1423)

Commits

• 760013e Fix timestamp issue in test_check_source_is_newer_when_using_jupytext_sync (#...
• 2a9162d Transition to Pixi
• f412847 Version 1.18.0
• 860d9c0 Add an example jupyterlab-slideshow notebook
• b39919e Test Jupytext with Python 3.14 (#1457)
• 72ed864 Support formats lists for subset-specific notebook pairing (#1453)
• 0b453a3 Add more tests to demonstrate the pairing, including on Windows
• f96cfec Revert "Fix Windows path separator issue in paired notebooks (#1454)"
• 3b47cde Fix Windows path separator issue in paired notebooks (#1454)
• bc4f23e Fix AttributeError when raw cell contains non-dict YAML content (#1451)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions