Allow pure-addon schema-v2 dependency workspaces - #89
Merged
Conversation
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
1 participant
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
tool.uv.workspace.membersarray when no tenant or shared addon Python projects are discoveredmemberskey, exact discovered-member equality, tracked regular inputs, and offline uv lock currentnessWhy
The first CM Website artifact canary after #88 proved that uv accepts and locks a root-only virtual workspace, while devkit rejected
members = []. That made the schema-v2 requirement impossible for a pure Odoo addon with no Python package metadata.Validation
uv run python -m unittest discover -s tests— 218 passed, 1 skippeduv run ruff check .uv run ruff format --check .uv builduv run platform --helpplatform dependencies check—current=true,publishable=true, zero projects/membersPart of #87.