-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"latest" Docker image broken by #587 #595
Comments
maresb
added a commit
to conda/conda-lock
that referenced
this issue
Feb 10, 2023
`latest` is broken <mamba-org/quetz#595>
maresb
added a commit
to conda/conda-lock
that referenced
this issue
Feb 10, 2023
Pin Quetz Docker image used in tests `latest` is broken <mamba-org/quetz#595>
We made Quetz compatible with SQLAlchemy >=2.0 in v0.6.0. Can you give this another try, please? |
maresb
added a commit
to conda/conda-lock
that referenced
this issue
Feb 16, 2023
Reverts #343 now that <mamba-org/quetz#595> is fixed
Yes, it's working, thanks! |
maresb
added a commit
to conda/conda-lock
that referenced
this issue
Feb 16, 2023
Reverts #343 now that <mamba-org/quetz#595> is fixed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
About one day ago, the Quetz Docker image was rebuilt. In this image, SQLAlchemy v2.0.2 is installed. This triggers #587. (This is causing the conda-lock CI to fail conda/conda-lock#338.)
The text was updated successfully, but these errors were encountered: