Release 2.5.0

Offen
  • Stimmt etwas nicht?
#4,388 2 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
2/5
Geschätzter Aufwand
1-3 Stunden
Anfängerfreundlichkeit
25/100
Issue-Typ
Feature
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Bereich
release

Rechercherichtung

Read the release instructions in RELEASING.md, especially the manual editing section. The issue shows preparation, the release branch, and RC0 as complete, with only “Tag Final” unchecked; the available /promote command is described in the issue. Done when the final release task is complete.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

type: release

Release tasks

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.

  • #4401

Slack announcement

Greetings Pythonistas,

rules_python 2.5.0-rc0 ([bzlmod](https://registry.bazel.build/modules/rules_python/2.5.0-rc0), [workspace](https://github.com/bazel-contrib/rules_python/releases/tag/2.5.0-rc0)) is now available
[Changelog](https://rules-python.readthedocs.io/en/2.5.0-rc0/changelog.html#v2-5-0)

Notable changes:

- Bazel 10 is now fully supported.
- Added `pytest_test` to run pytest based tests.
- Added `:py_pbs_distribution` flag to select smaller stripped Python runtimes.
- `uv` can be invoked with `bazel run @rules_python//python/uv/bin:uv` (or `bazel run @uv` with `use_repo()`).
- `uv` lock: added git sources, scoped `override-dependencies`, and various fixes.
- `py_wheel`: more makevars available to replace `select()` usages.
- Updated Gazelle's Python parser to support Python 3.14 PEP 758 syntax.

It will be promoted to stable next week, pending feedback.

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.

Vorherrschende Sprache
Starlark
Sterne
692
Forks
734
Ø Merge
11 Std. 2 Min.
Gemergte PRs (30 T.)
150

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus bazel-contrib/rules_python

Alle Issues in bazel-contrib/rules_python

Ähnliche Issues

Weitere Issues zu Release

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.