Skip to content

Update code for Bazel change --incompatible_new_actions_api#2074

Merged
jayconrod merged 1 commit intobazel-contrib:masterfrom
laurentlb:master
May 23, 2019
Merged

Update code for Bazel change --incompatible_new_actions_api#2074
jayconrod merged 1 commit intobazel-contrib:masterfrom
laurentlb:master

Conversation

@laurentlb
Copy link
Copy Markdown
Contributor

Fixes #2071

Copy link
Copy Markdown
Collaborator

@jayconrod jayconrod left a comment

Choose a reason for hiding this comment

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

I'm okay with hotfixing, this, but let's leave #2071 open. I'll comment on that issue.

@jayconrod jayconrod merged commit ddea1ad into bazel-contrib:master May 23, 2019
yushan26 pushed a commit to yushan26/rules_go that referenced this pull request Jun 16, 2025
Before this PR the `uv` toolchain could not be used in a `genrule` it
seems because the `//python/uv:toolchain` does not have the necessary
providers for using the make variables and the re-exporting of the make
variables from the `toolchain` in the `current_toolchain` rule did not
seem to work.

This PR removes the provider construction in the `toolchain` and does
that only in the `current_toolchain`. This better mirrors how the Python
toolchains are setup (grepping `PYTHON3` is sufficient to get examples).
This also splits out work done in bazel-contrib#2059 to decrease its scope, so that
this can be discussed separately.

Work towards bazel-contrib#1975
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

rules_go depends on an old version of Skylib

3 participants