Migrate Automatic Exec Groups by adding a toolchain parameter to the affected actions#10514
Migrate Automatic Exec Groups by adding a toolchain parameter to the affected actions#10514ejona86 merged 3 commits intogrpc:masterfrom
Conversation
|
I can see that this PR request fails with |
|
Yeah, we support the two most recent versions. So we'll drop Bazel 5.x in January. |
|
Okay, that means we should not add |
|
@ejona86 @sergiitk I'm interested in when this change will be inside a new release since it's needed for my further migration of Automatic Exec Groups. Do you maybe know when can this happen approximately? |
|
@kotlaja, v1.59.0 was scheduled for this past Tuesday. It was delayed because of some conversations with protobuf. It looks like it was released yesterday. Release notes and notification are still in the works, but the release is available. |
This is a step forward for the full migration of Automatic Exec Groups (AEGs). This change will be effective once AEGs are enabled.
Goal of this migration:
toolchainattribute.I've added
Nonesince the executable (protoc) seems not to be from a real toolchain. Moreover, the rule itself doesn't register any toolchains.Ref cl/559113276.