-
Notifications
You must be signed in to change notification settings - Fork 4
chore(deps): update duckdb requirement from <=1.4.1,>=0.10.0 to >=0.10.0,<=1.4.2 #256
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
Claude encountered an error —— View job I'll analyze this and get back to you. |
0ae7bee to
76cf555
Compare
|
Claude encountered an error —— View job I'll analyze this and get back to you. |
Updates the requirements on [duckdb](https://github.com/duckdb/duckdb-python) to permit the latest version. - [Release notes](https://github.com/duckdb/duckdb-python/releases) - [Changelog](https://github.com/duckdb/duckdb-python/blob/main/CHANGELOG.md) - [Commits](duckdb/duckdb-python@v1.3.0...v1.4.2) --- updated-dependencies: - dependency-name: duckdb dependency-version: 1.4.2 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]>
76cf555 to
31bc6ba
Compare
|
Claude encountered an error —— View job I'll analyze this and get back to you. |
|
Claude finished @dependabot[bot]'s task —— View job ✅ DuckDB Dependency Update Review CompleteSummaryThis is a safe and recommended dependency update from DuckDB v1.4.1 to v1.4.2 (patch release). Change AnalysisModified File: - "duckdb>=0.10.0,<=1.4.1",
+ "duckdb>=0.10.0,<=1.4.2",Impact Assessment1. Scope of Usage ✅
2. DuckDB v1.4.2 Changes (Bug Fix Release)Key Improvements:
Breaking Changes: ❌ None identified All changes are bug fixes and enhancements with no API-breaking modifications. Validation Results✅ Code Quality (All Passed)make lint
✅ Test Executionuv run pytest tests/aignostics/dataset/cli_test.py::test_cli_idc_indices -v
✅ Architecture Compliance
✅ CI/CD Status
Security & Compliance✅ No Security Issues
✅ License Compliance
Recommendations✅ APPROVE - Safe to MergeReasoning:
Post-Merge Actions
Additional NotesKnown Issue (Unrelated to This PR)There is a test collection error in ImportError: cannot import name 'SPECIAL_APPLICATION_ID' from 'tests.constants_test'This is a pre-existing issue on main branch and not caused by the DuckDB update. DuckDB Version Matrix
Review Checklist (Per CLAUDE.md)
Verdict: ✅ LGTM - Approve and merge when CI passes This dependency update follows best practices and improves the SDK's compatibility and stability without introducing any risks. |
Codecov Report✅ All modified and coverable lines are covered by tests. ❌ Your project check has failed because the head coverage (63.43%) is below the target coverage (70.00%). You can increase the head coverage or adjust the target coverage. |
|



Updates the requirements on duckdb to permit the latest version.
Release notes
Sourced from duckdb's releases.
Changelog
Sourced from duckdb's changelog.
Commits
70380a1Submodule at 68d7555 for 1.4.2 release13827e7Fix InsertRelation on attached database (#155)7ccc8e9Add explicit .pl(lazy=True) overload (#172)20bfd52review feedback10e0ef3Add explicit polars overloads95a9968Fix InsertRelation on attached databasef3b8c8aBumped submodulef5618a3Bumped submodule17a0cadremove experimental import because of the transitive dependencies that requirese35a2cemypy shouldn't check experimental.sparkDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)