Repository navigation
release duckdb-sqlalchemy 2.0.0 - #236
Conversation
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6e907354e1
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ## Maintained in this fork | ||
|
|
||
| ## Unreleased | ||
| ## [2.0.0](https://github.com/leonardovida/duckdb-sqlalchemy/compare/v1.5.6.11...v2.0.0) (2026-11-17) |
There was a problem hiding this comment.
Restore the Unreleased changelog section
When the next user-visible change is prepared, contributors have no Unreleased section in CHANGELOG.md under which to record it, even though the repository requires every such change to add an entry there. Keep an empty ## Unreleased section above the new 2.0.0 release, as was done in docs/breaking-changes.md, so future changes can follow the documented release process.
AGENTS.md reference: AGENTS.md:L39-L41
Useful? React with 👍 / 👎.
Releases 2.0.0, the first version that supports DuckDB 2.0. The version follows the supported DuckDB line.
Changes
pyproject.tomlanduv.lock: version 2.0.0.CHANGELOG.md: the Unreleased entries move into the 2.0.0 section, with an "Upgrading from 1.5.6.11" section.docs/breaking-changes.md: the Unreleased entries move under 2.0.0, with an entry for the version number.No code changes. The features were merged in #234 and #235.
Test evidence
ruff,tyandpre-commit run --all-filespass.scripts/verify_distribution.pyon Python 3.13 in two fresh environments: a plain installation (resolves DuckDB 2.0.0) and[motherduck](resolves DuckDB 1.5.6).