Bump CAPI to v1.2.0 #4
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
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.
This makes this repository incompatible with duckdb
v1.1.3by bumping the headers and required CAPI version to v1.2.0.It would be probably better to park this is a separate branch, say v1.2, waiting actual release to make this branch the main branch.
What this PR does is making
extension-template-ccompatible with what would become releasev1.2.0by bumping from v0.0.1 to v1.2.0 the CAPI version.DuckDB headers have been fetched via
make update_duckdb_headersplus changes in duckdb/duckdb#15611 (to fix problems with windows symbol visibility).linux_amd64_musldo not work at the moment due to platform mismatch given tests are executed outside the container.Fix there is likely in extension-ci-tools and this repo.