Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Release 2.3.4

Open
#4,173 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Domain
release

Research direction

Read RELEASING.md, especially the changelog synchronization instructions and the manual editing section. Use the documented /sync-changelog command for #4156 on main, then verify that the unchecked changelog task is completed.

Written by the indexing model from the issue text.

Description

type: release

Release tasks

  • Sync #4156 to changelog on main
  • Update #4156 to changelog on release branch
  • Tag Final | status=done tag=2.3.4 commit= 7282b93c

Backports

To request or track a backport, comment /backport on the PR, comment
/backport <PR> on this issue, or add it to the checklist below. See
RELEASING.md: How to add backports
for details.

  • #4156 status=done

To manually control the release flow, see the
RELEASING.md: Manual Editing
section.

Available Commands

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.
  • /sync-changelog: Processes sync changelog tasks.
  • /backport <PRs>: Adds PRs to the backports and processes backports.
  • /promote: Promotes the latest RC to final release.

See RELEASING.md for details on how to use them.

Dominant language
Starlark
Stars
690
Forks
722
Avg merge
1d 55m
Merged PRs (30d)
38

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bazel-contrib/rules_python

All issues in bazel-contrib/rules_python

Similar issues

More Release issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.