fix(backend): bump duckdb dependencies #37
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
YogiPristiawan
approved these changes
May 26, 2024
| @@ -1,20 +1,17 @@ | |||
| FROM node:16.14.0-bullseye AS frontend | |||
| FROM node:16.14.0-bookworm AS frontend | |||
There was a problem hiding this comment.
Biar nggak masalah kalo urusan dengan Debian repositorynya.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I know that the modification of the migration script is something that's not allowed, but you gotta do what you gotta do.
So we're resolving this issue duckdb/duckdb#11756, in which the fix is here duckdb/duckdb#11821, and it's included on the duckdb upstream release a few days ago https://github.com/duckdb/duckdb/releases/tag/v0.10.3, and on the go binding, it's not released yet (marcboeker/go-duckdb@9aec71d), so we gotta pull from the commit hash.