Pin DuckDB submodule#35
Merged
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fix: https://github.com/duckdblabs/duckdb-internal/issues/9843
We're pinning the DuckDB submodule to point to
4ce2416bbf4996e191679c19316517ba03ce36f6(duckdb/duckdb@4ce2416) to not keep breaking the CI on every PR that tries to fetchmain, since there really is no need to keep up with bleeding edgemainat the moment.Once this is merged, the in-flight PRs should be updated with main.
#31 is pointing duckdb at an older commit, so it should remove the bump.
#33 is pointing at the same commit, so should not have any changes.