chore: prepare for 1.5 release (#2973)

Update version markers with upcoming version.

Author: rickeylev

CHANGELOG.md

@@ -47,12 +47,12 @@ BEGIN_UNRELEASED_TEMPLATE
 END_UNRELEASED_TEMPLATE
 -->
 
-{#v0-0-0}
-## Unreleased
+{#1-5-0}
+## [1.5.0] - 2025-06-11
 
-[0.0.0]: https://github.com/bazel-contrib/rules_python/releases/tag/0.0.0
+[1.5.0]: https://github.com/bazel-contrib/rules_python/releases/tag/1.5.0
 
-{#v0-0-0-changed}
+{#1-5-0-changed}
 ### Changed
 
 * (rules) On Windows, {obj}`--bootstrap_impl=system_python` is forced. This
@@ -66,7 +66,7 @@ END_UNRELEASED_TEMPLATE
   `PyInfo.site_packages_symlinks`
 * (deps) Updating setuptools to patch CVE-2025-47273.
 
-{#v0-0-0-fixed}
+{#1-5-0-fixed}
 ### Fixed
 
 * (rules) PyInfo provider is now advertised by py_test, py_binary, and py_library;
@@ -93,7 +93,7 @@ END_UNRELEASED_TEMPLATE
   by platform even though the same version is used. Fixes [#2648](https://github.com/bazel-contrib/rules_python/issues/2648).
 * (pypi) `compile_pip_requirements` test rule works behind the proxy
 
-{#v0-0-0-added}
+{#1-5-0-added}
 ### Added
 * Repo utilities `execute_unchecked`, `execute_checked`, and `execute_checked_stdout` now
   support `log_stdout` and `log_stderr` keyword arg booleans. When these are `True`
@@ -115,7 +115,7 @@ END_UNRELEASED_TEMPLATE
   Useful when an intermediate dependency needs to be upgraded to pull in
   security patches.
 
-{#v0-0-0-removed}
+{#1-5-0-removed}
 ### Removed
 * Nothing removed.
 

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

@@ -167,7 +167,7 @@ Default: `//python/config_settings:_pip_env_marker_default_config`
 This flag points to a target providing {obj}`EnvMarkerInfo`, which determines
 the values used when environment markers are resolved at build time.
 
-:::{versionadded} VERSION_NEXT_FEATURE
+:::{versionadded} 1.5.0
 :::
 ::::
 

docs/environment-variables.md

@@ -65,7 +65,7 @@ The default became `1` if unspecified
 When `1`, the rules_python Starlark implementation of the pypi/pip integration is used
 instead of the legacy Python scripts.
 
-:::{versionadded} VERSION_NEXT_FEATURE
+:::{versionadded} 1.5.0
 :::
 ::::
 

docs/toolchains.md

@@ -305,7 +305,7 @@ that can be used with `target_settings`. Some particular ones of note are:
 {flag}`--py_linux_libc` and {flag}`--py_freethreaded`, among others.
 :::
 
-:::{versionadded} VERSION_NEXT_FEATURE
+:::{versionadded} 1.5.0
 Added support for custom platform names, `target_compatible_with`, and
 `target_settings` with `single_version_platform_override`.
 :::

python/features.bzl

@@ -35,7 +35,7 @@ def _features_typedef():
 
     True if the `PyInfo.venv_symlinks` field is available.
 
-    :::{versionadded} VERSION_NEXT_FEATURE
+    :::{versionadded} 1.5.0
     :::
     ::::
 

python/private/local_runtime_toolchains_repo.bzl

@@ -96,7 +96,7 @@ conditions are met, typically values from `@platforms`.
 
 See the [Local toolchains] docs for examples and further information.
 
-:::{versionadded} VERSION_NEXT_FEATURE
+:::{versionadded} 1.5.0
 :::
 """,
         ),
@@ -145,7 +145,7 @@ The `target_settings` attribute, which handles `config_setting` values,
 instead of constraints.
 :::
 
-:::{versionadded} VERSION_NEXT_FEATURE
+:::{versionadded} 1.5.0
 :::
 """,
         ),
@@ -183,7 +183,7 @@ The `target_compatible_with` attribute, which handles *constraint* values,
 instead of `config_settings`.
 :::
 
-:::{versionadded} VERSION_NEXT_FEATURE
+:::{versionadded} 1.5.0
 :::
 """,
         ),

python/private/py_info.bzl

@@ -312,7 +312,7 @@ This field is currently unused in Bazel and may go away in the future.
 :::{include} /_includes/experimental_api.md
 :::
 
-:::{versionadded} VERSION_NEXT_FEATURE
+:::{versionadded} 1.5.0
 :::
 """,
     },

python/private/py_library.bzl

@@ -97,7 +97,7 @@ This attributes populates {obj}`PyInfo.venv_symlinks`.
 
 :::{versionadded} 1.4.0
 :::
-:::{versionchanged} VERSION_NEXT_FEATURE
+:::{versionchanged} 1.5.0
 The topological order has been removed and if 2 different versions of the same PyPI
 package are observed, the behaviour has no guarantees except that it is deterministic
 and that only one package version will be included.

python/private/py_runtime_info.bzl

@@ -334,7 +334,7 @@ to meet two criteria:
    interpreter. This typically requires the Python version to be known at
    build-time and match at runtime.
 
-:::{versionadded} VERSION_NEXT_FEATURE
+:::{versionadded} 1.5.0
 :::
 """,
         "zip_main_template": """

python/private/py_runtime_rule.bzl

@@ -360,7 +360,7 @@ Whether this runtime supports virtualenvs created at build time.
 
 See {obj}`PyRuntimeInfo.supports_build_time_venv` for docs.
 
-:::{versionadded} VERSION_NEXT_FEATURE
+:::{versionadded} 1.5.0
 :::
 """,
                 default = True,