Prepare v1.0.0 release - #1
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
1 participant
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.
Summary
httpfs, select the named Iceberg secret, quote identifiers, and support nested namespaces.env.*files and symlink targets from entering release ZIPsWhy
The generated attach script omitted required storage setup and could become ambiguous when multiple Iceberg secrets existed. Configurable SQL identifiers were also emitted without quoting. Local release packaging excluded only
.env, so variant env files and symlinks could disclose local data.Impact
DuckDB setup is safer and works with nested namespaces, while local and CI release artifacts avoid known secret-bearing files.
Validation
pytest: 7 passedruff check .: passedgit diff --check: passed