tree 5b384fa29d7e9e870c299255a9511332484de74b
parent 425082473e33d1c01c1581681ae14553790d9012
author Gowroji Sunil <sgowroji@google.com> 1694617540 +0530
committer GitHub <noreply@github.com> 1694617540 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJlAc/UCRBK7hj4Ov3rIwAA1B4IAGJIuEGGOI0BSwh88dESHPNg
 aqG7iTaQXQn7kF8AwZCuXLbePY5dfhmar7uVi2071++5A59X9gxyuF5u6j1j50tj
 E0L9uJ4tmry7r2jewikZylnQ5Sx6yTVeNznnG8or2dD/iOQrzEvKpRV/siiAbTtq
 x774PpPQyDdaoo3pJ8zFY3NXik0sb1wTqe0n6YcSvA+EBTw1pKHfkJ0fEs0qFypK
 mFah45QFriPLQqKDjvfiI2Sa2y/GvgXb0ZVsS1kOFqss35fsFRMZkAra9m/0PYNp
 Xh5bUMElvO+rSgX51lRvnzmr/aKIAVyX4TrqMTU5gDnUNntc5QrgVN9bvQbjCMU=
 =jn74
 -----END PGP SIGNATURE-----
 

fix(gazelle): upgrade rules_go: 0.39.1 -> 0.41.0 to work with upcoming Bazel versions (#1410)

This makes rules_python's usage of Go work with upcoming Bazel versions.
The
`_whitelist_function_transition` attribute in the Go rules is being
removed, per
https://github.com/bazelbuild/bazel/issues/19493. Newer Go rule releases
are compatible
with the upcoming Bazel versions.

Fixes : [1409](https://github.com/bazelbuild/rules_python/issues/1409)