tree 65c10da34bcc89e5e3efd2ddcc6b8fc5b84e9c8b
parent 9e59206e806ca8e06cb9761358c90a0faadf7773
author Thulio Ferraz Assis <3149049+f0rmiga@users.noreply.github.com> 1692743034 -0700
committer GitHub <noreply@github.com> 1692743034 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJk5TWJCRBK7hj4Ov3rIwAArHcIADPURc1rbnDqnmx3pKTSyEbR
 QY3BKd4i6BGGzWlknqAcZQOIxVI+YhS1Oax130vODCwQgJPvhhbHcBlGjGF1OyFB
 jT1M0Wuy5NIl724VNerl1oa+zf+i87ZrcYSSN1OzxnukGRfjIp34Zk+49JQu9lna
 uMCF8eKdFur5Eoozk7363HA6j1/BMoC4qdQoNL9UQmYHOizHDKocs7nEuULa/pOy
 9EbO/zJdGEiSKazFfIIqOPcUdIrxkycSdLYIl/OF4MX4whM/mDWmWlVPeBGUszzW
 An2juvYVpamPu84pm0euFspjeZp4MmEXjWkbDm/+ouJC7T1g2mv20bJWM/nFUv8=
 =pL1I
 -----END PGP SIGNATURE-----
 

fix: bcr releaser email (#1392)

Fixes https://github.com/bazelbuild/bazel-central-registry/pull/863.

The aspect email is no longer associated with the github user, so the
CLA bot but doesn't
think think the CLA is signed. To fix, change the email the BCR PRs are
published under
to an address that is associated with the github user (and thus the
CLA).