Skip to content

bug: Do not require projects that use rules_uv as transitive dependency to always have bazel_dep(rules_uv) - #302

Merged
markelliot merged 2 commits into
bazel-contrib:mainfrom
shayanhoshyari:patch-1
Dec 1, 2025
Merged

markelliot merged 2 commits into
bazel-contrib:mainfrom
shayanhoshyari:patch-1

Conversation

@shayanhoshyari

@shayanhoshyari shayanhoshyari commented Nov 30, 2025

Copy link
Copy Markdown
Contributor

Describe the issue

#303

Solution

Because rules_uv directly reference @rules_uv. sing Label(...) addresses this.

Relative reference does not work since this is a macro, and it will resolve in the caller project.

@shayanhoshyari shayanhoshyari changed the title bug: Do not require projects that use rules_uv as transitive dependency to always have bazel_dep(rules_uv) [WIP] bug: Do not require projects that use rules_uv as transitive dependency to always have bazel_dep(rules_uv) Nov 30, 2025
@shayanhoshyari shayanhoshyari changed the title [WIP] bug: Do not require projects that use rules_uv as transitive dependency to always have bazel_dep(rules_uv) bug: Do not require projects that use rules_uv as transitive dependency to always have bazel_dep(rules_uv) Nov 30, 2025

@markelliot markelliot left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

thanks

@markelliot
markelliot enabled auto-merge (squash) December 1, 2025 00:56
@markelliot
markelliot merged commit 5019aa6 into bazel-contrib:main Dec 1, 2025
7 of 9 checks passed
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.

2 participants