fix: properly write metadata in async geoparquet writer #928
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
gadomski
changed the title
Merged
gadomski
pushed a commit
that referenced
this pull request
Jan 6, 2026
## 🤖 New release
* `stac`: 0.15.1 -> 0.16.0 (⚠ API breaking changes)
* `stac-io`: 0.2.1 -> 0.2.2 (✓ API compatible changes)
* `stac-server`: 0.4.1 -> 0.4.2 (✓ API compatible changes)
* `stac-validate`: 0.6.1 -> 0.6.2 (✓ API compatible changes)
* `rustac`: 0.2.1 -> 0.2.2
* `stac-duckdb`: 0.3.1 -> 0.3.2
* `pgstac`: 0.4.1 -> 0.4.2
* `stac-extensions`: 0.1.3 -> 0.1.4
### ⚠ `stac` breaking changes
```text
--- failure pub_module_level_const_missing: pub module-level const is missing ---
Description:
A public const is missing or renamed
ref: https://doc.rust-lang.org/cargo/reference/semver.html#item-remove
impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.45.0/src/lints/pub_module_level_const_missing.ron
Failed in:
VERSION in file /tmp/.tmp59pq4i/stac/src/geoarrow/mod.rs:23
VERSION_KEY in file /tmp/.tmp59pq4i/stac/src/geoarrow/mod.rs:20
```
<details><summary><i><b>Changelog</b></i></summary><p>
## `stac`
<blockquote>
##
[0.16.0](stac-v0.15.1...stac-v0.16.0)
- 2026-01-05
### Added
- [**breaking**] write collections to stac-geoparquet metadata
([#927](#927))
- datetime expansion
([#917](#917))
### Fixed
- properly write metadata in async geoparquet writer
([#928](#928))
</blockquote>
## `stac-io`
<blockquote>
##
[0.2.2](stac-io-v0.2.1...stac-io-v0.2.2)
- 2026-01-05
### Fixed
- references, not ownership, in geoparquet store writer
([#929](#929))
- properly write metadata in async geoparquet writer
([#928](#928))
</blockquote>
## `stac-server`
<blockquote>
##
[0.4.2](stac-server-v0.4.1...stac-server-v0.4.2)
- 2026-01-05
### Other
- *(deps)* update reqwest requirement from 0.12.8 to 0.13.1
([#926](#926))
</blockquote>
## `stac-validate`
<blockquote>
##
[0.6.2](stac-validate-v0.6.1...stac-validate-v0.6.2)
- 2026-01-05
### Other
- update Cargo.toml dependencies
</blockquote>
## `rustac`
<blockquote>
##
[0.2.2](rustac-v0.2.1...rustac-v0.2.2)
- 2026-01-05
### Added
- datetime expansion
([#917](#917))
</blockquote>
## `stac-duckdb`
<blockquote>
##
[0.3.2](stac-duckdb-v0.3.1...stac-duckdb-v0.3.2)
- 2026-01-05
### Other
- updated the following local packages: stac
</blockquote>
## `pgstac`
<blockquote>
##
[0.4.2](pgstac-v0.4.1...pgstac-v0.4.2)
- 2026-01-05
### Other
- updated the following local packages: stac
</blockquote>
## `stac-extensions`
<blockquote>
##
[0.1.4](stac-extensions-v0.1.3...stac-extensions-v0.1.4)
- 2026-01-05
### Other
- updated the following local packages: stac
</blockquote>
</p></details>
---
This PR was generated with
[release-plz](https://github.com/release-plz/release-plz/).
Co-authored-by: stac-utils-release-bot[bot] <249776822+stac-utils-release-bot[bot]@users.noreply.github.com>
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.
No description provided.