uv build
should output information about built artifacts in machine-readable form.
#12392
Labels
enhancement
New feature or improvement to existing functionality
Summary
I would like to use
uv build
as part of a pipeline (in particular, in a GitHub action, but this doesn't matter particularly) and further process the built artifacts. Right now, I have a couple of non-ideal options for this:Successfully built
dist/
directory before runninguv build
and then afterwards use a glob or something to get all the files in that directory, and assume that nothing extra snuck inIt would be good if
uv
could output the paths to the built artifacts in a machine-readable form (JSON? but I don't really care which). Alternatively, perhaps the built paths could be output on stdout, so no parsing is necessary to get the paths. (This would have the classic problem of filenames with newlines being problematic, but I'm not sure if that's really an issue here.)Example
These are just examples, I'm not particularly concerned about exact formats
or
The text was updated successfully, but these errors were encountered: