fix: stray references to rules_protoc

Author: alexeagle

.github/workflows/release.yml

@@ -12,4 +12,4 @@ jobs:
   release:
     uses: bazel-contrib/.github/.github/workflows/release_ruleset.yaml@v6
     with:
-      release_files: rules_protoc-*.tar.gz
+      release_files: toolchains_protoc-*.tar.gz

.github/workflows/release_prep.sh

@@ -8,8 +8,8 @@ TAG=${GITHUB_REF_NAME}
 # The prefix is chosen to match what GitHub generates for source archives
 # This guarantees that users can easily switch from a released artifact to a source archive
 # with minimal differences in their code (e.g. strip_prefix remains the same)
-PREFIX="rules_protoc-${TAG:1}"
-ARCHIVE="rules_protoc-$TAG.tar.gz"
+PREFIX="toolchains_protoc-${TAG:1}"
+ARCHIVE="toolchains_protoc-$TAG.tar.gz"
 
 # NB: configuration for 'git archive' is in /.gitattributes
 git archive --format=tar --prefix=${PREFIX}/ ${TAG} | gzip > $ARCHIVE
@@ -35,7 +35,7 @@ http_archive(
     name = "toolchains_protoc",
     sha256 = "${SHA}",
     strip_prefix = "${PREFIX}",
-    url = "https://github.com/alexeagle/rules_protoc/releases/download/${TAG}/${ARCHIVE}",
+    url = "https://github.com/alexeagle/toolchains_protoc/releases/download/${TAG}/${ARCHIVE}",
 )
 EOF
 

CONTRIBUTING.md

@@ -28,19 +28,19 @@ Run `bazel run //:gazelle` to keep them up-to-date.
 ## Using this as a development dependency of other rules
 
 You'll commonly find that you develop in another WORKSPACE, such as
-some other ruleset that depends on rules_protoc, or in a nested
+some other ruleset that depends on toolchains_protoc, or in a nested
 WORKSPACE in the integration_tests folder.
 
 To always tell Bazel to use this directory rather than some release
 artifact or a version fetched from the internet, run this from this
 directory:
 
 ```sh
-OVERRIDE="--override_repository=rules_protoc=$(pwd)/rules_protoc"
+OVERRIDE="--override_repository=toolchains_protoc=$(pwd)/toolchains_protoc"
 echo "common $OVERRIDE" >> ~/.bazelrc
 ```
 
-This means that any usage of `@rules_protoc` on your system will point to this folder.
+This means that any usage of `@toolchains_protoc` on your system will point to this folder.
 
 ## Releasing
 

README.md

@@ -52,4 +52,4 @@ common --incompatible_enable_proto_toolchain_resolution
 ```
 
 Follow instructions from the release you wish to use:
-<https://github.com/alexeagle/rules_protoc/releases>
+<https://github.com/alexeagle/toolchains_protoc/releases>

e2e/smoke/WORKSPACE.bazel

@@ -7,9 +7,9 @@ local_repository(
 #---SNIP--- Below here is re-used in the workspace snippet published on releases
 
 ######################
-# rules_protoc setup #
+# toolchains_protoc setup #
 ######################
-# Fetches the rules_protoc dependencies.
+# Fetches the toolchains_protoc dependencies.
 # If you want to have a different version of some dependency,
 # you should fetch it *before* calling this.
 # Alternatively, you can skip calling this function, so long as you've