Warn when workspace member scripts are skipped due to missing build system#18389
Merged
charliermarsh merged 3 commits intoastral-sh:mainfrom Mar 10, 2026
Merged
Conversation
zsol
requested changes
Mar 10, 2026
terror
changed the title
terror
changed the title
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
3 participants
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.
Resolves #18388
When a workspace member declares
[project.scripts]without a[build-system]table ortool.uv.package = true, uv silently skips installing those entry points. The warning that normally fires for the root project was never emitted for non-root workspace members, because the check only inspected the workspace root'spyproject.toml.This diff replaces the single-project check with a loop over all workspace members, so the warning fires for any member that has scripts but is not packaged. The warning message now includes the package name to make it actionable when multiple members are involved.