chore: update changelog and version markers for 1.3 release (#2683)

rickeylev · web-flow · commit d976228abe36 · 2025-03-20T21:34:01.000Z
Updates the changelog and VERSION_NEXT_XXX markers to specify 1.3.0 for the upcoming release. Work towards #2683
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -45,21 +45,44 @@ Unreleased changes template.
 * Nothing removed.
 -->
 
+
 {#v0-0-0}
 ## Unreleased
 
 [0.0.0]: https://github.com/bazelbuild/rules_python/releases/tag/0.0.0
 
 {#v0-0-0-changed}
 ### Changed
+* Nothing changed.
+
+{#v0-0-0-fixed}
+### Fixed
+* Nothing fixed.
+
+{#v0-0-0-added}
+### Added
+* Nothing added.
+
+{#v0-0-0-removed}
+### Removed
+* Nothing removed.
+
+
+{#v1-3-0}
+## Unreleased
+
+[1.3.0]: https://github.com/bazelbuild/rules_python/releases/tag/1.3.0
+
+{#v1-3-0-changed}
+### Changed
 * (deps) platforms 0.0.4 -> 0.0.11
 * (py_wheel) Package `py_library.pyi_srcs` (`.pyi` files) in the wheel.
 * (py_package) Package `py_library.pyi_srcs` (`.pyi` files) in `py_package`.
 * (gazelle) The generated manifest file (default: `gazelle_python.yaml`) will now include the
   YAML document start `---` line. Implemented in
   [#2656](https://github.com/bazelbuild/rules_python/pull/2656).
 
-{#v0-0-0-fixed}
+{#v1-3-0-fixed}
 ### Fixed
 * (pypi) The `ppc64le` is now pointing to the right target in the `platforms` package.
 * (gazelle) No longer incorrectly merge `py_binary` targets during partial updates in
@@ -76,7 +99,7 @@ Unreleased changes template.
   creating `.pyc` files.
 * (deps) doublestar 4.7.1 (required for recent Gazelle versions)
 
-{#v0-0-0-added}
+{#v1-3-0-added}
 ### Added
 * {obj}`//python/bin:python`: convenience target for directly running an
   interpreter. {obj}`--//python/bin:python_src` can be used to specify a
@@ -102,7 +125,7 @@ Unreleased changes template.
 * (rules) Added {obj}`main_module` attribute to `py_binary` and `py_test`,
   which allows specifying a module name to run (i.e. `python -m <module>`).
 
-{#v0-0-0-removed}
+{#v1-3-0-removed}
 ### Removed
 * Nothing removed.
 
diff --git a/docs/api/rules_python/python/bin/index.md b/docs/api/rules_python/python/bin/index.md
@@ -30,7 +30,7 @@ bazel run @rules_python//python/bin:python \
 The {flag}`--python_src` flag for using the intepreter a binary/test uses.
 ::::
 
-::::{versionadded} VERSION_NEXT_FEATURE
+::::{versionadded} 1.3.0
 ::::
 :::
 
diff --git a/docs/environment-variables.md b/docs/environment-variables.md
@@ -24,7 +24,7 @@ python /path/to/debugger.py --port 12345 --file /path/to/file.py
 The {bzl:obj}`interpreter_args` attribute.
 :::
 
-:::{versionadded} VERSION_NEXT_FEATURE
+:::{versionadded} 1.3.0
 
 ::::
 
diff --git a/python/api/executables.bzl b/python/api/executables.bzl
@@ -16,7 +16,7 @@
 {#python-apis-executables-bzl}
 Loading-phase APIs specific to executables (binaries/tests).
 
-:::{versionadded} VERSION_NEXT_FEATURE
+:::{versionadded} 1.3.0
 :::
 """
 
diff --git a/python/api/libraries.bzl b/python/api/libraries.bzl
@@ -16,7 +16,7 @@
 {#python-apis-libraries-bzl}
 Loading-phase APIs specific to libraries.
 
-:::{versionadded} VERSION_NEXT_FEATURE
+:::{versionadded} 1.3.0
 :::
 """
 
diff --git a/python/private/attr_builders.bzl b/python/private/attr_builders.bzl
@@ -14,7 +14,7 @@
 
 """Builders for creating attributes et al.
 
-:::{versionadded} VERSION_NEXT_FEATURE
+:::{versionadded} 1.3.0
 :::
 """
 
diff --git a/python/private/py_binary_rule.bzl b/python/private/py_binary_rule.bzl
@@ -34,7 +34,7 @@ def create_py_binary_rule_builder():
     :::{include} /_includes/volatile_api.md
     :::
 
-    :::{versionadded} VERSION_NEXT_FEATURE
+    :::{versionadded} 1.3.0
     :::
 
     Returns:
diff --git a/python/private/py_executable.bzl b/python/private/py_executable.bzl
@@ -102,7 +102,7 @@ Only supported for {obj}`--bootstrap_impl=script`. Ignored otherwise.
 The {obj}`RULES_PYTHON_ADDITIONAL_INTERPRETER_ARGS` environment variable
 :::
 
-:::{versionadded} VERSION_NEXT_FEATURE
+:::{versionadded} 1.3.0
 :::
 """,
         ),
@@ -146,7 +146,7 @@ information about running modules as the main program.
 
 This is mutually exclusive with {obj}`main`.
 
-:::{versionadded} VERSION_NEXT_FEATURE
+:::{versionadded} 1.3.0
 :::
 """,
         ),
@@ -1803,7 +1803,7 @@ def create_executable_rule_builder(implementation, **kwargs):
     and the output is something that can be run directly (e.g. `bazel run`,
     `exec(...)` etc)
 
-    :::{versionadded} VERSION_NEXT_FEATURE
+    :::{versionadded} 1.3.0
     :::
 
     Returns:
diff --git a/python/private/py_library.bzl b/python/private/py_library.bzl
@@ -151,7 +151,7 @@ def create_py_library_rule_builder():
     :::{include} /_includes/volatile_api.md
     :::
 
-    :::{versionadded} VERSION_NEXT_FEATURE
+    :::{versionadded} 1.3.0
     :::
 
     Returns:
diff --git a/python/private/py_test_rule.bzl b/python/private/py_test_rule.bzl
@@ -37,7 +37,7 @@ def create_py_test_rule_builder():
     :::{include} /_includes/volatile_api.md
     :::
 
-    :::{versionadded} VERSION_NEXT_FEATURE
+    :::{versionadded} 1.3.0
     :::
 
     Returns:
diff --git a/python/private/pypi/attrs.bzl b/python/private/pypi/attrs.bzl
@@ -20,7 +20,7 @@ ATTRS = {
         doc = """
 If true, add the lib dir of the bundled interpreter to the library search path via `LDFLAGS`.
 
-:::{versionadded} VERSION_NEXT_FEATURE
+:::{versionadded} 1.3.0
 :::
 """,
     ),
diff --git a/python/private/rule_builders.bzl b/python/private/rule_builders.bzl
@@ -92,7 +92,7 @@ def create_custom_foo_binary():
 custom_foo_binary = create_custom_foo_binary()
 ```
 
-:::{versionadded} VERSION_NEXT_FEATURE
+:::{versionadded} 1.3.0
 :::
 """
 
