Skip to content

Conversation

edgarrmondragon
Copy link
Contributor

Do let me know if you think this is beyond the scope of this action, cause this is specific to uv-managed packages.

Related

@edgarrmondragon edgarrmondragon marked this pull request as draft September 2, 2025 22:21
@edgarrmondragon edgarrmondragon changed the title Support build all or specific packages in a uv workspace Support building all or specific packages in a uv workspace Sep 2, 2025
Copy link
Contributor

@jamesbraza jamesbraza left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@edgarrmondragon I like this, thanks for the contribution.

Here's my current usage: https://github.com/Future-House/aviary/blob/v0.23.0/.github/workflows/publish.yml. For each package I invoke BAIPP then actions/download-artifact. So after this PR I can invoke BAIPP once 👍 , then how would I use .outputs.artifact-name if --all-packages was specified? Or would I just have to individually invoke actions/download-artifact with hardcoded package name inputs

(*optional*, default: `'false'`).
- `package`: The package to build.
If not specified, the package in the current directory is built.
If set to `all`, all packages in the `uv` [workspace](https://docs.astral.sh/uv/concepts/workspaces/) are built.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wdyt of adding a note that one can use uv tree --depth 0 to view all packages in the current workspace?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Building 2+ packages at once

3 participants