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.
This release adds support for generating lockfiles from Jupyter notebooks using inline metadata, as defined in PEP 723.
By default, notebooks remain unlocked. To lock a notebook, run
juv lock /path/to/notebook.ipynb
, which generates and embeds a lockfile in the notebook's metadata under the"uv.lock"
key. The lockfile is respected and updated automatically when usingjuv run
,uv add
, oruv remove
.Additional commands:
juv export
: Outputs an alternative lockfile format (requirements.txtstyle) to stdout.
uv tree
: Displays the dependency tree for a script.Both commands work with notebooks, whether locked or unlocked.
This release is considered breaking due to the lockfile support, which requires a minimum
uv
0.5.18 and modifies execution.