Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Resolve every tool's versions through the tool-versions data

Aperta
  • Qualcosa non va?
#7,887 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
docker, github, typescript
Ambito
devops, tooling

Direzione di ricerca

Start by reading the resolver changes in #7826 and the embedded fallback work in #7825, then trace the tool-version data flow between containerbase/base and containerbase/tool-versions. Compare tools with registry lookups, swallowed errors, or special constraints such as Poetry's plugin range. Done means every tool resolves latest, partial, and exact versions through online data with embedded fallback, while respecting release age and tool-specific limits.

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

Descrizione

What would you like containerbase to do?

Give every tool a version resolver and resolve all of them through the tool-versions data.

Today the tools are covered unevenly:

  • some tools have no resolver and only get the generic partial-version lookup from #7826

  • some resolvers only handle latest (php, composer, mise)

  • some resolvers catch their own lookup errors and keep the input, so the embedded fallback from #7825 never runs (nuget, gradle, maven, pip), eg. install-tool nuget 6.11 downloads v6.11 when tools.json can't be reached

  • some resolvers apply more than a version lookup, which the embedded fallback skips, eg. poetry's latest respects the version range of poetry-plugin-pypi-mirror, the offline fallback picks the newest embedded release

Required changes

  • one resolver per tool, based on the tool-versions data (online first, embedded as fallback)
  • latest, partial and exact versions resolve the same way for every tool
  • lookup errors aren't swallowed, the shared fallback handles them
  • tool-specific limits, like poetry's plugin range, also apply to versions from the tool-versions data
  • a minimum release age (eg. 1 hour) for latest and partial versions, so a new release isn't picked before all its downloads are reachable: in tool-versions when publishing, and in resolvers that still ask a registry directly. Eg. install-pip pipenv 2026 resolved to 2026.10.2 from the PyPI JSON api 6½ minutes after the upload, while pip's index still ended at 2026.10.1.
  • drop the interim partial flag from #7826

Some resolutions change for users, eg. a partial version that was used as is resolves to the newest matching release. That is accepted, the embedded data keeps installs working when the online lookup fails.

Part of #7768.

Drafted by Claude Opus 5.5 (Claude Code) for @viceice.

Lingua principale
TypeScript
Stelle
58
Fork
65
Merge medio
10h 37m
PR unite (30g)
462

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

  • Include un Dockerfile o un file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

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 containerbase/base

Tutte le issue di containerbase/base

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.