[BUG] Version manager sets different version in different folders in Docker
@kay-schecker ya está trabajando en esto.
Desde el 19/1/2024.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
🐛 Bug Report:
Describe the bug
I am running the CLI as part of a Bitbucket pipeline in a Docker container. The v7.2.0 update broke our pipeline because of an Axios version update. It's easy enough to set the openapi-generator version back to v7.1.0 using openapi-generator-cli version-manager set 7.1.0. I put this line in my Dockerfile.
However, I saw that v7.2.0 was still being used. Debugging it locally by building the Docker container and attaching to it, I see at the root level, openapi-generator-cli version is set to 7.1.0, but changing to a copied-in folder where the pipeline work is done, the version is 7.2.0.
Steps to Reproduce
Steps to reproduce the behavior:
- Build a Docker container where openapi-generator-cli is installed via npm, and the openapi-generator version is set to a version other than the latest (7.2.0 at time of writing).
- Attach to Docker container and check version of openapi-generator the CLI is using.
- Switch directories
- Check the version of openapi-generator being used
Expected behavior
The openapi-generator version should be the same, regardless of directory
Operation System (please complete the following information):
- Docker image from node:16.20.1-alpine
Package System (please complete the following information):
- NPM v8.19.4
- openapi-generator-cli v2.8.0
Additional context
The following commands are in my Docker file to install and set the CLI
RUN npm install -g @openapitools/openapi-generator-cli@2.8.0
RUN openapi-generator-cli version-manager set 7.1.0
- Lenguaje dominante
- TypeScript
- Estrellas
- 2k
- Forks
- 208
- Merge medio
- 7 h 12 min
- PR fusionados (30 d)
- 6
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
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.
Más de OpenAPITools/openapi-generator-cli
-
[FEATURE] consider using caret ranges instead of pinned exact versions for runtime dependencies Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
bug
OpenAPITools/openapi-generator-cli#1213 · 1 asignado ·
-
bug
OpenAPITools/openapi-generator-cli#1190 · 1 asignado ·
-
bug
OpenAPITools/openapi-generator-cli#1138 · 1 comentario · 1 asignado ·
-
bug
OpenAPITools/openapi-generator-cli#1094 · 1 comentario · 1 asignado ·
Todos los issues de OpenAPITools/openapi-generator-cli
Issues similares
-
bug(cli): hapi doctor inline-media prints a fabricated B:\ helper-script path in packaged installs Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
Crush Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 85/100
catppuccin/catppuccin#3125 ·
-
Add a SECURITY.md Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
ElementsProject/cln-application#167 · 1 comentario · 1 reacción ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Quantco/pnpm-licenses#17 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100