chore: prepare 1.9.0 release (#3623)

Updating version markers and changelog for 1.9.0 release

Author: rickeylev

CHANGELOG.md

@@ -47,16 +47,16 @@ BEGIN_UNRELEASED_TEMPLATE
 END_UNRELEASED_TEMPLATE
 -->
 
-{#v0-0-0}
-## Unreleased
+{#v1-9-0}
+## [1.9.0] - 2026-02-21
 
-[0.0.0]: https://github.com/bazel-contrib/rules_python/releases/tag/0.0.0
+[1.9.0]: https://github.com/bazel-contrib/rules_python/releases/tag/1.9.0
 
-{#v0-0-0-removed}
+{#v1-9-0-removed}
 ### Removed
 * Nothing removed.
 
-{#v0-0-0-changed}
+{#v1-9-0-changed}
 ### Changed
 * **DEPRECATED: implicit zipapp support**
   * Implicit zipapp output of `py_binary`/`py_test` has been deprecated and
@@ -81,15 +81,15 @@ END_UNRELEASED_TEMPLATE
   `config_settings` attribute. NOTE: `enable_runfiles=true` will
   soon become **required for Windows**.
 
-{#v0-0-0-fixed}
+{#v1-9-0-fixed}
 ### Fixed
 * (runfiles) Fixed `CurrentRepository()` raising `ValueError` on Windows.
   ([#3579](https://github.com/bazel-contrib/rules_python/issues/3579))
 * (tests) No more coverage warnings are being printed if there are no sources.
   ([#2762](https://github.com/bazel-contrib/rules_python/issues/2762))
 * (gazelle) Ancestor `conftest.py` files are added in addition to sibling `conftest.py`.
   ([#3497](https://github.com/bazel-contrib/rules_python/issues/3497)) Note
-  that this behavior can be reverted to the pre-VERSION_NEXT_FEATURE behavior by setting the new
+  that this behavior can be reverted to the pre-1.9.0 behavior by setting the new
   `python_include_ancestor_conftest` directive to `false`.
 * (pypi) `pip_parse` no longer silently drops PEP 508 URL-based requirements
   (`pkg @ https://...`) when `extract_url_srcs=False` (the default for
@@ -100,7 +100,7 @@ END_UNRELEASED_TEMPLATE
   ([#3587](https://github.com/bazel-contrib/rules_python/issues/3587))
 * (binaries/tests) Stamped build data generated by Windows actions is readable
 
-{#v0-0-0-added}
+{#v1-9-0-added}
 ### Added
 * (binaries/tests) {obj}`--debugger`: allows specifying an extra dependency
   to add to binaries/tests for custom debuggers.
@@ -127,7 +127,7 @@ END_UNRELEASED_TEMPLATE
 * (gazelle) A new directive `python_include_ancestor_conftest` has been added.
   When `false`, ancestor `conftest` targets are not automatically added to
   {bzl:obj}`py_test` target dependencies. This `false` behavior is how things
-  were in `rules_python` before VERSION_NEXT_FEATURE. The default is `true`, as the prior behavior
+  were in `rules_python` before 1.9.0. The default is `true`, as the prior behavior
   was technically incorrect.
   ([#3596](https://github.com/bazel-contrib/rules_python/pull/3596))
 
@@ -2203,4 +2203,4 @@ Breaking changes:
 * (pip) Create all_data_requirements alias
 * Expose Python C headers through the toolchain.
 
-[0.24.0]: https://github.com/bazel-contrib/rules_python/releases/tag/0.24.0
+[0.24.0]: https://github.com/bazel-contrib/rules_python/releases/tag/0.24.0

docs/api/rules_python/python/config_settings/index.md

@@ -62,7 +62,7 @@ Setting this flag adds the debugger dependency, but doesn't automatically set
 `PYTHONBREAKPOINT` to change `breakpoint()` behavior.
 :::
 
-:::{versionadded} VERSION_NEXT_FEATURE
+:::{versionadded} 1.9.0
 :::
 ::::
 

gazelle/docs/directives.md

@@ -753,7 +753,7 @@ Detailed docs are not yet written.
 (directive-python-include-ancestor-conftest)=
 ## `python_include_ancestor_conftest`
 
-Version VERSION_NEXT_FEATURE includes a fix ({gh-pr}`3498`) for a long-standing issue
+Version 1.9.0 includes a fix ({gh-pr}`3498`) for a long-standing issue
 ({gh-issue}`3497`) where ancestor `conftest.py` files were not automatically
 added as dependencies of {bzl:obj}`py_test` targets.
 
@@ -762,7 +762,7 @@ Thus the `python_include_ancestor_conftest` directive controls this behavior.
 It defaults to `true`, which causes all ancestor `conftest.py` files to be
 included as dependencies for {bzl:obj}`py_test` targets.
 
-Setting the directive to `false` reverts to the pre-VERSION_NEXT_FEATURE behavior.
+Setting the directive to `false` reverts to the pre-1.9.0 behavior.
 
 For example, given this directory tree (not shown: intermediary `BUILD.bazel`
 files)

python/features.bzl

@@ -79,7 +79,7 @@ def _features_typedef():
 
     Whether the rules_python version has the `py_zipapp_*` rules
 
-    :::{versionadded} VERSION_NEXT_FEATURE
+    :::{versionadded} 1.9.0
     ::::
     """
 

python/private/py_exec_tools_info.bzl

@@ -50,7 +50,7 @@ may be removed.
 
 The Python runtime to use for the exec configuration.
 
-:::{versionadded} VERSION_NEXT_FEATURE
+:::{versionadded} 1.9.0
 
 In prior versions, the equivalent can be obtained using:
 ```

python/private/py_executable_info.bzl

@@ -24,7 +24,7 @@ rules provide it directly so that the runtime the binary original chose
 can be accessed.
 :::
 
-:::{versionadded} VERSION_NEXT_FEATURE
+:::{versionadded} 1.9.0
 :::
 """,
         "build_data_file": """
@@ -38,7 +38,7 @@ A symlink to build_data.txt if stamping is enabled, otherwise None.
 Args that should be passed to the interpreter before regular args
 (e.g. `-X whatever`).
 
-:::{versionadded} VERSION_NEXT_FEATURE
+:::{versionadded} 1.9.0
 :::
 """,
         "interpreter_path": """
@@ -75,7 +75,7 @@ The Bazel-executable-level entry point to the program, which handles Bazel-speci
 setup before running the file in {obj}`main`. May be None if a two-stage bootstrap
 implementation isn't being used.
 
-:::{versionadded} VERSION_NEXT_FEATURE
+:::{versionadded} 1.9.0
 :::
 """,
         "venv_python_exe": """
@@ -84,7 +84,7 @@ implementation isn't being used.
 The `bin/python3` file within the venv this binary uses. May be None if venv
 mode is not enabled.
 
-:::{versionadded} VERSION_NEXT_FEATURE
+:::{versionadded} 1.9.0
 :::
 """,
     },

python/private/zipapp/py_zipapp_rule.bzl

@@ -337,7 +337,7 @@ Output groups:
   the previous implicit zipapp functionality. Set `executable=False`
   and use the default output of the target instead.*
 
-:::{versionadded} VERSION_NEXT_FEATURE
+:::{versionadded} 1.9.0
 :::
 """.lstrip()
 

python/py_binary.bzl

@@ -28,7 +28,7 @@ def py_binary(**attrs):
     * `srcs_version`: cannot be `PY2` or `PY2ONLY`
     * `tags`: May have special marker values added, if not already present.
 
-    :::{versionchanged} VERSION_NEXT_FEATURE
+    :::{versionchanged} 1.9.0
     The `PYTHONBREAKPOINT` environment variable is inherited. Use in combination
     with {obj}`--debugger` to customize the debugger available and used.
     :::

python/zipapp/py_zipapp_binary.bzl

@@ -12,7 +12,7 @@ load("//python/private/zipapp:py_zipapp_rule.bzl", _py_zipapp_binary_rule = "py_
 def py_zipapp_binary(**kwargs):
     """Builds a Python zipapp from a py_binary/py_test target.
 
-    :::{versionadded} VERSION_NEXT_FEATURE
+    :::{versionadded} 1.9.0
     :::
 
     Args:

python/zipapp/py_zipapp_test.bzl

@@ -12,7 +12,7 @@ load("//python/private/zipapp:py_zipapp_rule.bzl", _py_zipapp_test = "py_zipapp_
 def py_zipapp_test(**kwargs):
     """Builds a Python zipapp from a py_binary/py_test target.
 
-    :::{versionadded} VERSION_NEXT_FEATURE
+    :::{versionadded} 1.9.0
     :::
 
     Args: