Implement `registry-version-check` script

Ouverte
  • Quelque chose ne va pas ?
#426 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

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

@thomashoneyman y travaille déjà.

Depuis le 22/7/2026.

  • #786 par @thomashoneyman — ouverte

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
45/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
À l'abandon
Domaine
tooling

Piste de recherche

Start by locating the registry's script entry points and the proposed Registry.Scripts.VersionCheck module. Read the most recent package set from the package-sets repository and inspect the registry's metadata directory. Done means identifying packages whose latest registry version exceeds the package-set version and logging those versions to the console.

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

Description

CI help wanted

The packaging team regularly makes manual package sets releases. Manual releases are required, for example, when a package such as Halogen is upgraded. Invariably the new Halogen version will break other packages in the set, and so the Halogen release is not added at first. Over time the dependents upgrade to the new Halogen, at which point Halogen and its dependents can all be updated in one go to produce a new package set.

The packaging team needs to be able to tell what package versions have been uploaded to the registry and are more recent than the version of those packages in the package set. For example, if Halogen 6 is in the package set and Halogen 7 has been released (but could not be added automatically because it breaks downstream packages), then we need to be able to tell that there's a Halogen 7 release waiting to go into the package set.

To accomplish this, we need to add a new script to the registry. This script, most likely named Registry.Scripts.VersionCheck, should:

  1. Read in the contents of the most recent package set (this can be read from the package-sets repository for now, but it will use the registry in the future)
  2. Read in the contents of the metadata directory in the registry
  3. Find all packages with a latest version higher than its version in the package set
  4. Log those package versions to the console for review
Langage dominant
PureScript
Étoiles
95
Forks
79
Merge moyen
16 h 13 min
PR mergées (30 j)
14

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 purescript/registry-dev

Toutes les issues de purescript/registry-dev

Issues similaires

Plus d'issues DevTools

Recevez les nouvelles issues par e-mail

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