Merge branch 'main' into feat/starlark-env-marker-and-metadata-parsing

Author: aignas

.bcr/gazelle/metadata.template.json

@@ -1,9 +1,9 @@
 {
-    "homepage": "https://github.com/bazelbuild/rules_python",
+    "homepage": "https://github.com/bazel-contrib/rules_python",
     "maintainers": [
         {
             "name": "Richard Levasseur",
-            "email": "rlevasseur@google.com",
+            "email": "richardlev@gmail.com",
             "github": "rickeylev"
         },
         {
@@ -13,7 +13,8 @@
         }
     ],
     "repository": [
-        "github:bazelbuild/rules_python"
+        "github:bazelbuild/rules_python",
+        "github:bazel-contrib/rules_python"
     ],
     "versions": [],
     "yanked_versions": {}

.bcr/metadata.template.json

@@ -1,9 +1,9 @@
 {
-  "homepage": "https://github.com/bazelbuild/rules_python",
+  "homepage": "https://github.com/bazel-contrib/rules_python",
   "maintainers": [
     {
       "name": "Richard Levasseur",
-      "email": "rlevasseur@google.com",
+      "email": "richardlev@gmail.com",
       "github": "rickeylev"
     },
     {
@@ -13,7 +13,8 @@
     }
   ],
   "repository": [
-    "github:bazelbuild/rules_python"
+    "github:bazelbuild/rules_python",
+    "github:bazel-contrib/rules_python"
   ],
   "versions": [],
   "yanked_versions": {}

.github/workflows/create_archive_and_notes.sh

@@ -17,8 +17,8 @@ set -o errexit -o nounset -o pipefail
 
 # Exclude dot directories, specifically, this file so that we don't
 # find the substring we're looking for in our own file.
-# Exclude CONTRIBUTING.md because it documents how to use these strings.
-if grep --exclude=CONTRIBUTING.md --exclude-dir=.* VERSION_NEXT_ -r; then
+# Exclude CONTRIBUTING.md, RELEASING.md because they document how to use these strings.
+if grep --exclude=CONTRIBUTING.md --exclude=RELEASING.md --exclude-dir=.* VERSION_NEXT_ -r; then
   echo
   echo "Found VERSION_NEXT markers indicating version needs to be specified"
   exit 1
@@ -72,7 +72,7 @@ http_archive(
     name = "rules_python",
     sha256 = "${SHA}",
     strip_prefix = "${PREFIX}",
-    url = "https://github.com/bazelbuild/rules_python/releases/download/${TAG}/rules_python-${TAG}.tar.gz",
+    url = "https://github.com/bazel-contrib/rules_python/releases/download/${TAG}/rules_python-${TAG}.tar.gz",
 )
 
 load("@rules_python//python:repositories.bzl", "py_repositories")
@@ -90,7 +90,7 @@ http_archive(
     name = "rules_python_gazelle_plugin",
     sha256 = "${SHA}",
     strip_prefix = "${PREFIX}/gazelle",
-    url = "https://github.com/bazelbuild/rules_python/releases/download/${TAG}/rules_python-${TAG}.tar.gz",
+    url = "https://github.com/bazel-contrib/rules_python/releases/download/${TAG}/rules_python-${TAG}.tar.gz",
 )
 
 # To compile the rules_python gazelle extension from source,

.github/workflows/mypy.yaml

@@ -22,11 +22,10 @@ jobs:
       - uses: jpetrucciani/mypy-check@master
         with:
           requirements: 1.6.0
-          python_version: 3.8
+          python_version: 3.9
           path: 'python/runfiles'
       - uses: jpetrucciani/mypy-check@master
         with:
           requirements: 1.6.0
-          python_version: 3.8
+          python_version: 3.9
           path: 'tests/runfiles'
-      

.github/workflows/release.yml

@@ -33,7 +33,7 @@ jobs:
           # This special value tells pypi that the user identity is supplied within the token
           TWINE_USERNAME: __token__
           # Note, the PYPI_API_TOKEN is for the rules-python pypi user, added by @rickylev on
-          # https://github.com/bazelbuild/rules_python/settings/secrets/actions
+          # https://github.com/bazel-contrib/rules_python/settings/secrets/actions
           TWINE_PASSWORD: ${{ secrets.PYPI_API_TOKEN }}
         run: bazel run --stamp --embed_label=${{ github.ref_name }} //python/runfiles:wheel.publish
       - name: Release

BZLMOD_SUPPORT.md

@@ -11,7 +11,7 @@ In general `bzlmod` has more features than `WORKSPACE` and users are encouraged
 
 ## Configuration
 
-The releases page will give you the latest version number, and a basic example.  The release page is located [here](/bazelbuild/rules_python/releases).
+The releases page will give you the latest version number, and a basic example.  The release page is located [here](/bazel-contrib/rules_python/releases).
 
 ## What is bzlmod?
 
@@ -53,7 +53,7 @@ better supported.
 the toolchains rules_python registers**.
 
 NOTE: Regardless of your toolchain, due to
-[#691](https://github.com/bazelbuild/rules_python/issues/691), `rules_python`
+[#691](https://github.com/bazel-contrib/rules_python/issues/691), `rules_python`
 still relies on a local Python being available to bootstrap the program before
 handing over execution to the toolchain Python.