Run "oldest dependencies tests" CI in all PRs

Fermée
#1,868 0 commentaires 0 réactions 1 personne assignée Voir sur GitHub

Les mainteneurs répondent en général sous 4 jours

@Sevans711 y travaille déjà.

Depuis le 2/11/2026.

  • #1869 par @Sevans711 — fusionnée

Évaluation

Cette issue n'a pas encore été évaluée.

Description

CI dependencies developer experience

The oldest dependencies tests CI added in #1781 (AKA "minimum dependency tests") ensure that uxarray actually supports using the oldest possible versions of packages which are allowed by the pins in pyproject.toml.

However, the test is currently not automatically run in most PRs, due to the paths: restriction of only running when pyproject.toml or .github/workflows/min-deps-ci.yml are updated. This means that issues easily go unnoticed, and surface later during unrelated work. For example, #1823 introduced tests which fail on xarray<2025.11.0, but didn't raise the version pin accordingly. Instead of surfacing directly in that PR, this surfaced in #1852, #1866, and #1867. Additionally, any discovery about changes failing on older versions must still be done manually, such as in https://github.com/UXARRAY/uxarray/pull/1803#discussion_r4416769869, or it will go unnoticed until later.

The test itself seems to have a comparable duration to existing CI tests, as it mostly just installing dependencies and running the pytest test suite, it's just that the installed dependencies happen to be the oldest allowed versions instead of the newest allowed versions. Knowing that the duration is similar, it makes more sense to me to have it run in all PRs directly, so that these issues can be spotted immediately when they are introduced, instead of requiring various issue reports and hotfixes later.

Langage dominant
Python
Étoiles
232
Forks
59
Merge moyen
6 j 4 h
PR mergées (30 j)
18

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 UXARRAY/uxarray

Toutes les issues de UXARRAY/uxarray

Issues similaires

Plus d'issues Python

Recevez les nouvelles issues par e-mail

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