Implement `registry-version-check` script

Aberta
  • Algo errado?
#426 1 comentário 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

@thomashoneyman já está trabalhando nisso.

Desde 22/7/2026.

  • #786 de @thomashoneyman — aberto

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
45/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Estagnada
Domínio
tooling

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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
Linguagem predominante
PureScript
Estrelas
95
Forks
79
Merge médio
16h 13min
PRs com merge (30d)
14

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de purescript/registry-dev

Todas as issues de purescript/registry-dev

Issues semelhantes

Mais issues de DevTools

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.