tree 1fa0917cbde9ed9e167e10be9360653c691a68b7
parent 929b8d9d54a2db6fbe27b72dca4e71a30e820199
author Alexandre Rostovtsev <arostovtsev@google.com> 1685557227 -0400
committer GitHub <noreply@github.com> 1685557227 -0400
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJkd4/rCRBK7hj4Ov3rIwAAKpwIAC7KCxeTPAp2Sh46rnExmHBJ
 tjos/BEaSg47dWByUcpgOHm+YmeeIfEzIcFqBeEyQ41o5Eks5u0AR3g2oTQUmZjS
 +sJ43xtuBAcCUz79TktT+2iF94fYKWPwT2sR5PHoXM6RKWVy4fmvQNRnON7u6eoZ
 gQQOiL0G22bw2OYxTOsYuBpETNGmLO1vj83xCCEzyWY+jqqSQ2yX0VZvHGaj5led
 jFLI4rL+o89nfcOFE6lwysb1uYAjBfGNXvbhaRa55+zH/CmbMShzFW8RwintaQFK
 DR5ISfIG++CSrIZkPYKTyuiwgYMT/hHqcPswZX9GYiyWZwaO3i+4rVYIqqUX+uU=
 =tvbD
 -----END PGP SIGNATURE-----
 

Prepare release 0.5.5 with java toolchains breakage fix for Bazel at HEAD (#158)

Update rules_java dep to fix "No matching toolchains" errors with Bazel at HEAD, i.e. after https://github.com/bazelbuild/bazel/commit/975866a3e09212766bd353a90a8c42efe91d53ab

This error warrants an immediate release because it affects users of Stardoc releases, not just Stardoc itself.

See https://buildkite.com/bazel/bazel-skylib/builds/2692#0188728a-5bf4-4bb0-8d3a-6bc726a54f26 for an example failure.