# Release tasks - [x] Sync Changelog #4043 | status=done pr= #4058 - [x] Tag Final | status=done tag=2.3.1 commit= 3ed66a5c ## Backports To request a backport, add it to the checklist below and process it. See [RELEASING.md: How to add backports](https://github.com/bazel-contrib/rules_python/blob/main/RELEASING.md#how-to-add-backports) for details. - [x] #4043 | status=done rc=rc0 commit= 3ed66a5c --- To manually control the release flow, see the [RELEASING.md: Manual Editing](https://github.com/bazel-contrib/rules_python/blob/main/RELEASING.md#manual-editing-of-tracking-issue) section. <details> <summary><b>Available Commands</b></summary> Comment commands: - `/prepare`: Determines version, creates tracking issue and preparation PR. - `/prepare-complete [PR]`: Marks preparation task as complete. - `/create-release-branch`: Cuts and pushes the release branch. - `/create-rc`: Tags and publishes a new release candidate (RC). - `/process-backports`: Cherry-picks pending backports. - `/add-backports <PRs>`: Adds PRs to the backports and processes backports. - `/promote`: Promotes the latest RC to final release. See [RELEASING.md](https://github.com/bazel-contrib/rules_python/blob/main/RELEASING.md) for details on how to use them. </details>
Activity
rickeylev commentedon Aug 14, 2026
/process-backports
fix(pypi): do not return rctx.metadata for pip_archive (#4043)
rickeylev commentedon Aug 14, 2026
/promote
github-actions commentedon Aug 14, 2026
New Release Tagged! 🐍🌿
Version 2.3.1 has been successfully generated and tagged on branch
release/2.3.