Release 2.5.0

Aperta
  • Qualcosa non va?
#4,388 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Ambito
release

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Starlark
Stelle
692
Fork
734
Merge medio
11h 2m
PR unite (30g)
150

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di bazel-contrib/rules_python

Tutte le issue di bazel-contrib/rules_python

Issue simili

Altre issue su Release

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.