tree 718908827dde325655d4c734397c9c35cfbcecbb
parent 4e32e70a700dac5b41e05ed6e9429e49ebb1a4ee
author Alex Eagle <alex@aspect.dev> 1699369300 -0800
committer GitHub <noreply@github.com> 1699369300 +0100
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJlSlFUCRBK7hj4Ov3rIwAADJkIACeA/Z8qGo3Ra5dKnvjgVbxw
 IwOvKTZCbJkQWUrKq7/es/g95aMscDoryC/PePeeBVyUlGrmPNctkUP1YSR7sHsN
 fa4YBUYaIb+XxkfOYIxzxrrP/ggeIsoJiBtj3oNdVll+xL313ordsjMbiiVrZ8/m
 JCJrlJOX2BaSQdMGhaSv3BBdS1yYqYpTYUwCRxxzcof0M1lqxGDYuSlRbUW7Kh9b
 880tbzhu0tKESMEqC48TTAnj36vB+GdaiBlFkIyqLwvYBHezZkZ84LN2P7wfOUIj
 ArRCE7chntkFLiwnChBjQzW2v3V/5npkxVQ87StywWEqTykmWC/pc34B/yPfklM=
 =dQM0
 -----END PGP SIGNATURE-----
 

chore: add config for Publish to BCR app (#193)

Now that releases are automated, the release doesn't have an author, so
the app can't figure out whose fork of bazel-central-registry the PR
should originate from.

This will fix the error from publishing 6.0.0-rc0 to the BCR.