Remove MODULE.bazel version bump from release process (bazelbuild#2017)

It turns out it really doesn't matter what this version is in the repo,
so we can simplify our release process a bit by not needing to generate
this file, or merge a PR updating it

Author: keith

.github/update-module-version.sh

@@ -18,18 +18,6 @@ jobs:
         run: |
           set -euo pipefail
 
-          git config user.name "Automatic version bump"
-          git config user.email "[email protected]"
-
-          ./.github/update-module-version.sh "$TAG"
-          tmp_branch="$(uuidgen)"
-          git checkout -b "$tmp_branch"
-          git add MODULE.bazel
-          msg="Update MODULE.bazel to $TAG"
-          git commit -m "$msg"
-          git push -u origin "$tmp_branch"
-          gh pr create --title "$msg" --body ""
-
           COPYFILE_DISABLE=1 tar czvf "rules_apple.$TAG.tar.gz" ./*
           ./.github/generate-notes.sh "$TAG" | tee notes.md
           gh release create "$TAG" --title "$TAG" --target "$GITHUB_REF_NAME" --notes-file notes.md "rules_apple.$TAG.tar.gz"

.github/workflows/create-release.yml

@@ -112,8 +112,6 @@ is the recommended process:
 - Update the `apple/repositories.bzl` and `MODULE.bazel` files in `rules_apple` with the new
   `apple_support` and `rules_swift` releases.
 - Repeat the steps above to create a release on `rules_apple`.
-- Merge the automatically submitted PRs that update the `MODULE.bazel`
-  versions.
 
 ### Notes
 

MAINTENANCE.md

@@ -1,14 +1,11 @@
-# Generated by update-module-version.sh. DO NOT EDIT.
 module(
     name = "rules_apple",
-    version = "2.4.1",
+    version = "0",
     bazel_compatibility = [">=6.0.0"],
     compatibility_level = 1,
     repo_name = "build_bazel_rules_apple",
 )
 
-# --- End generated content
-
 bazel_dep(name = "bazel_skylib", version = "1.3.0")
 bazel_dep(name = "apple_support", version = "1.7.1", repo_name = "build_bazel_apple_support")
 bazel_dep(name = "rules_swift", version = "1.9.1", repo_name = "build_bazel_rules_swift")