Skip to content

Conversation

carlopi
Copy link
Contributor

@carlopi carlopi commented Jul 7, 2025

On top of #18161 (now merged), small bump further to handle limitation of linking in duckb-wasm solved via (duckdb/duckdb-spatial#634)

@carlopi
Copy link
Contributor Author

carlopi commented Jul 7, 2025

Discussed with @Maxxen: this is a nice to have change that touches only duckdb-wasm surface, not a blocker.

@carlopi carlopi changed the title Bump spatial again: include re-linkinng for handling global objects in Wasm Bump spatial again: include re-linking for handling global objects in Wasm Jul 7, 2025
@Mytherin Mytherin merged commit 9592335 into duckdb:v1.3-ossivalis Jul 7, 2025
49 checks passed
@Mytherin
Copy link
Collaborator

Mytherin commented Jul 7, 2025

Thanks!

github-actions bot pushed a commit to duckdb/duckdb-r that referenced this pull request Jul 12, 2025
Allow explicit compression for user types (duckdb/duckdb#18219)
Skip logging test for smaller block sizes (duckdb/duckdb#18201)
Add VS2019 compat flag to Python wheel build (duckdb/duckdb#18198)
Bump Julia to v1.3.2 (duckdb/duckdb#18185)
Bump spatial again: include re-linking for handling global objects in Wasm (duckdb/duckdb#18170)
github-actions bot added a commit to duckdb/duckdb-r that referenced this pull request Jul 12, 2025
Allow explicit compression for user types (duckdb/duckdb#18219)
Skip logging test for smaller block sizes (duckdb/duckdb#18201)
Add VS2019 compat flag to Python wheel build (duckdb/duckdb#18198)
Bump Julia to v1.3.2 (duckdb/duckdb#18185)
Bump spatial again: include re-linking for handling global objects in Wasm (duckdb/duckdb#18170)

Co-authored-by: krlmlr <krlmlr@users.noreply.github.com>
@carlopi carlopi deleted the bump-spatial-v1.3.2-bis branch August 17, 2025 20:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants