Pin uv upper bound to <0.8.0 to preserve Jupyter static asset layering
#96
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.
uv 0.8.0 introduced a breaking change that affects how
uv run --withinvocations work. The new version creates an additional ephemeral environment layer on top of the cached environment, which breaks our ability to access layered Jupyter static assets from the virtual environments that uv creates.juv relies on uv's previous behavior where the layered virtual environments were directly accessible, allowing us to combine Jupyter static assets from multiple environment layers. The new ephemeral environment prevents this access pattern.
We'll need to find an alternative approach for accessing layered Jupyter static assets before removing this upper bound.