Release 2.5.0

Ouverte
  • Quelque chose ne va pas ?
#4,388 2 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
2/5
Temps estimé
1-3 heures
Accessibilité débutants
25/100
Type d'issue
Fonctionnalité
Clarté
Clairement spécifiée
Activité
Active
Domaine
release

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
Starlark
Étoiles
692
Forks
734
Merge moyen
11 h 2 min
PR mergées (30 j)
150

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de bazel-contrib/rules_python

Toutes les issues de bazel-contrib/rules_python

Issues similaires

Plus d'issues Release

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.