`update.sh` updates all versions for non-matching version input
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- Dockerfile
- Estrellas
- 8.6k
- Forks
- 2k
- Merge medio
- 10 h 19 min
- PR fusionados (30 d)
- 16
Descripción
Environment
- Platform: Ubuntu 24.04.4 LTS
- Docker Version: N/A
- Node.js Version: 24.14.1
- Image Tag: N/A
Expected Behavior
If the update.sh script is run using a MAJOR_VERSION that is not set up, such as 23 (EOL) or 26 (not yet released), the script should fail with an error message.
Current Behavior
The script acts as though no MAJOR_VERSION was specified and updates all available versions.
Possible Solution
Steps to Reproduce
Execute:
./update.sh -s 26
Additional Information
Logs
$ ./update.sh -s 26
Updating version 20...
Updating version 22...
Updating version 24...
Updating version 25...
20/bookworm-slim/Dockerfile is already up to date!
20/bookworm/Dockerfile is already up to date!
20/bullseye-slim/Dockerfile is already up to date!
20/bullseye/Dockerfile is already up to date!
20/trixie-slim/Dockerfile is already up to date!
20/trixie/Dockerfile is already up to date!
22/trixie/Dockerfile is already up to date!
22/bookworm/Dockerfile is already up to date!
22/trixie-slim/Dockerfile is already up to date!
22/bookworm-slim/Dockerfile is already up to date!
22/bullseye/Dockerfile is already up to date!
22/bullseye-slim/Dockerfile is already up to date!
24/bullseye-slim/Dockerfile is already up to date!
24/bookworm-slim/Dockerfile is already up to date!
24/bookworm/Dockerfile is already up to date!
25/bullseye/Dockerfile is already up to date!
25/bookworm/Dockerfile is already up to date!
24/bullseye/Dockerfile is already up to date!
24/trixie-slim/Dockerfile is already up to date!
24/trixie/Dockerfile is already up to date!
25/bookworm-slim/Dockerfile is already up to date!
25/trixie/Dockerfile is already up to date!
25/bullseye-slim/Dockerfile is already up to date!
25/trixie-slim/Dockerfile is already up to date!
20/alpine3.22/Dockerfile is already up to date!
22/alpine3.22/Dockerfile is already up to date!
22/alpine3.23/Dockerfile is already up to date!
20/alpine3.23/Dockerfile is already up to date!
25/alpine3.23/Dockerfile is already up to date!
24/alpine3.22/Dockerfile is already up to date!
24/alpine3.23/Dockerfile is already up to date!
25/alpine3.22/Dockerfile is already up to date!
Done!
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Línea de trabajo
Empieza leyendo update.sh y concéntrate en cómo se analiza el argumento -s MAJOR_VERSION y cómo se compara con las versiones disponibles. Ejecuta ./update.sh -s 26 para reproducir el comportamiento actual y, después, verifica que las versiones no compatibles, como 23 o 26, fallen con un error, mientras que las versiones compatibles continúan actualizándose con normalidad.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- docker, shell
- Área
- build-system, devops
- Tipo de issue
- Error
- Dificultad
- 2/5
- Tiempo estimado
- 1-3 horas
- Estado de actividad
- Tranquilo
- Claridad
- Bien especificado
- Aptitud para principiantes
- 64/100