Skip to content

Bump the python-minor-and-patch group across 1 directory with 11 updates - #10

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/uv/python-minor-and-patch-95615fe5be
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/uv/python-minor-and-patch-95615fe5be

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 19, 2026

Copy link
Copy Markdown

Bumps the python-minor-and-patch group with 11 updates in the / directory:

Package From To
typer 0.27.3 0.29.1
dbt-core 1.12.6 1.12.7
dbt-duckdb 1.11.0 1.11.1
clickhouse-connect 1.11.0 1.12.0
dbt-bigquery 1.12.1 1.12.3
dbt-snowflake 1.12.3 1.12.5
pyarrow 26.0.0 26.0.1
dlt 1.31.0 1.32.0
airbyte-cdk 7.38.0 7.48.0
pytest 9.1.1 9.2.0
ruff 0.17.1 0.17.5

Updates typer from 0.27.3 to 0.29.1

Release notes

Sourced from typer's releases.

0.29.1

Typer includes an official skill that helps coding agents use new features and recommended patterns for your installed version. Install it with uvx library-skills in your project. See Develop with AI.

Upgrades

Docs

Internal

0.29.0

Features

  • ✨ Use Pydantic for parameter validation. PR #1831 by @​svlandeg.

    Typer now uses Pydantic internally to validate command-line parameters. This is a gradual migration focused on preserving compatibility with existing Typer applications. Some validation error messages, help text, and usage output have changed.

    Compatibility changes:

    • Pydantic >=2.5.3 is now a required dependency.
    • click_type has been removed from typer.Option() and typer.Argument(). New ways to provide custom types will be provided with Pydantic, with much more flexibility.
    • Some defaults are now validated more strictly. The previous tuple example's (None, None, None) default now fails validation. Use tuple[str, int, bool] | None with a default of None and check for None before unpacking, as shown in the updated tuple example. This also makes the code more correct, so you could consider this a bug fix, but if you depended on this behavior, there's a change needed in your code.
    • Default datetime parsing now follows Pydantic's rules, accepting Unix timestamps, timezone offsets, and fractional seconds.
    • Callback parameter objects no longer expose Click's .type, .make_metavar(), .human_readable_name, or .type_cast_value(). Custom integrations using these need updating.

Fixes

  • 🐛 Escape terminal controls in Pydantic validation errors. PR #2005 by @​tiangolo.

Docs

0.28.0

Fixes

  • 🐛 Ensure that the default option name is not changed by setting a metavar. PR #1957 by @​svlandeg.

Docs

... (truncated)

Changelog

Sourced from typer's changelog.

0.29.1 (2026-11-11)

Upgrades

Docs

Internal

0.29.0 (2026-11-09)

Features

  • ✨ Use Pydantic for parameter validation. PR #1831 by @​svlandeg.

    Typer now uses Pydantic internally to validate command-line parameters. This is a gradual migration focused on preserving compatibility with existing Typer applications. Some validation error messages, help text, and usage output have changed.

    Compatibility changes:

    • Pydantic >=2.5.3 is now a required dependency.
    • click_type has been removed from typer.Option() and typer.Argument(). New ways to provide custom types will be provided with Pydantic, with much more flexibility.
    • Some defaults are now validated more strictly. The previous tuple example's (None, None, None) default now fails validation. Use tuple[str, int, bool] | None with a default of None and check for None before unpacking, as shown in the updated tuple example. This also makes the code more correct, so you could consider this a bug fix, but if you depended on this behavior, there's a change needed in your code.
    • Default datetime parsing now follows Pydantic's rules, accepting Unix timestamps, timezone offsets, and fractional seconds.
    • Callback parameter objects no longer expose Click's .type, .make_metavar(), .human_readable_name, or .type_cast_value(). Custom integrations using these need updating.

Fixes

  • 🐛 Escape terminal controls in Pydantic validation errors. PR #2005 by @​tiangolo.

Docs

0.28.0 (2026-11-06)

Fixes

  • 🐛 Ensure that the default option name is not changed by setting a metavar. PR #1957 by @​svlandeg.

... (truncated)

Commits

Updates dbt-core from 1.12.6 to 1.12.7

Release notes

Sourced from dbt-core's releases.

dbt v1.12.7

dbt-core 1.12.7 - November 12, 2026

Features

  • Extend RunResult with the state_decision_id attribute (#0)

Fixes

  • Fall back to per-source freshness checks when batch metadata freshness computation fails, instead of skipping every selected source now that skip_nodes_if_on_run_start_fails defaults to True (#15634)
  • Scope relation-cache population in compile/show/docs generate to the selected nodes' schemas so --cache-selected-only is honored (previously only run respected the flag) (#12944)
  • Fix statically_parse_unrendered_config stringifying list/dict config values, which caused false positives in state:modified comparisons across different dbt versions. (#16133)
  • Reword the snapshot timestamp data type mismatch warning to identify hard-delete timestamps as the affected columns and to recommend overriding the snapshot_get_time macro, instead of incorrectly suggesting a change to the snapshot's updated_at config (#fs-14450)
  • Recognize Databricks Python model config keys (access_control_list, notebook_access_control_list) in jsonschema validation so they no longer raise spurious CustomKeyInConfigDeprecation warnings (dbt-databricks#1661) (#N/A)
  • Add the builtin_macros_prefer_overrides behavior flag (default false). When enabled and the macro search package is itself internal (e.g. dbt or dbt_postgres, as for builtin macros run via adapter.execute_macro), the adapter override is preferred over the base dbt implementation and a root-project macro always wins. It is off by default because a root-project macro that shares a builtin's name can otherwise hijack calls made inside dbt's own macros. (#16540)
  • Accept the dbt v2-only info_schema, check-paths and checks keys in dbt_project.yml, ignoring them with a note that they are specific to the dbt v2 engine (#16640)
  • Ignore manifest nodes with resource types dbt-core doesn't support, such as dbt v2 checks, when loading a manifest for --state and --defer (#16849)
  • Supply credentials for dbt deps git packages through a git credential helper instead of embedding them in the clone URL, so clones of redirecting repositories keep working with libcurl 7.81.0-1ubuntu1.30 and later (#16861)
  • Recognize Databricks use_materialization_v2 config in JSON schema validation (#16879)
  • Fix dbt deps failing with "could not read Username" when installing a git package from a subdirectory with credentials in the URL, by supplying credentials to the checkout's git reset --hard as well (#16861)
  • Recognize supported dbt State configurations on snapshots and data tests during JSON schema validation (#N/A)

Dependencies

  • Bump dbt-core-experimental-parser lowerbound to 2.0.11 (#17117)

Contributors

Changelog

Sourced from dbt-core's changelog.

dbt-core 1.12.7 - November 12, 2026

Features

  • Extend RunResult with the state_decision_id attribute (#0)

Fixes

  • Fall back to per-source freshness checks when batch metadata freshness computation fails, instead of skipping every selected source now that skip_nodes_if_on_run_start_fails defaults to True (#15634)
  • Scope relation-cache population in compile/show/docs generate to the selected nodes' schemas so --cache-selected-only is honored (previously only run respected the flag) (#12944)
  • Fix statically_parse_unrendered_config stringifying list/dict config values, which caused false positives in state:modified comparisons across different dbt versions. (#16133)
  • Reword the snapshot timestamp data type mismatch warning to identify hard-delete timestamps as the affected columns and to recommend overriding the snapshot_get_time macro, instead of incorrectly suggesting a change to the snapshot's updated_at config (#fs-14450)
  • Recognize Databricks Python model config keys (access_control_list, notebook_access_control_list) in jsonschema validation so they no longer raise spurious CustomKeyInConfigDeprecation warnings (dbt-databricks#1661) (#N/A)
  • Add the builtin_macros_prefer_overrides behavior flag (default false). When enabled and the macro search package is itself internal (e.g. dbt or dbt_postgres, as for builtin macros run via adapter.execute_macro), the adapter override is preferred over the base dbt implementation and a root-project macro always wins. It is off by default because a root-project macro that shares a builtin's name can otherwise hijack calls made inside dbt's own macros. (#16540)
  • Accept the dbt v2-only info_schema, check-paths and checks keys in dbt_project.yml, ignoring them with a note that they are specific to the dbt v2 engine (#16640)
  • Ignore manifest nodes with resource types dbt-core doesn't support, such as dbt v2 checks, when loading a manifest for --state and --defer (#16849)
  • Supply credentials for dbt deps git packages through a git credential helper instead of embedding them in the clone URL, so clones of redirecting repositories keep working with libcurl 7.81.0-1ubuntu1.30 and later (#16861)
  • Recognize Databricks use_materialization_v2 config in JSON schema validation (#16879)
  • Fix dbt deps failing with "could not read Username" when installing a git package from a subdirectory with credentials in the URL, by supplying credentials to the checkout's git reset --hard as well (#16861)
  • Recognize supported dbt State configurations on snapshots and data tests during JSON schema validation (#N/A)

Dependencies

  • Bump dbt-core-experimental-parser lowerbound to 2.0.11 (#17117)

Contributors

Commits
  • bd46c78 Bumping version to 1.12.7 and generate changelog
  • 7009713 feat: extend RunResult with the state_decision_id attribute (#15917) (#17136)
  • a2e1d40 Bump dbt-core-experimental-parser lowerbound to 2.0.11 (#17117) (#17157)
  • 065c043 Fix statically_parse_unrendered_config stringifying list/dict config … (#1628...
  • 8ea1e96 Fall back to per-source freshness when batch metadata computation fails (#156...
  • 8993e77 fix: reword snapshot timestamp mismatch warning to point at snapshot_get_time...
  • 93a1613 fix: scope compile/show/docs generate relation-cache population to selected s...
  • b482b64 ci: fix the macOS runner label (macos-14 retired) and the intermittent hatch ...
  • 4ddade3 Put builtin macro override resolution behind a behavior flag (#17056) (#17091)
  • 870af80 Backport State config schema coverage to 1.12 (#17034)
  • Additional commits viewable in compare view

Updates dbt-duckdb from 1.11.0 to 1.11.1

Release notes

Sourced from dbt-duckdb's releases.

1.11.1

What's Changed

New Contributors

Full Changelog: duckdb/dbt-duckdb@1.11.0...1.11.1

Changelog

Sourced from dbt-duckdb's changelog.

1.11.1 (2026-10-26)

  • Added support for motherduck_token as a top-level profile property
  • Fixed reruns of models referenced by a foreign key, which now rebuild the foreign key family instead of failing (upgrading: databases built by earlier versions need a one-time rebuild, since the first rerun can fail with Could not drop the table because this table is main key table of the table "<name>__dbt_tmp"; delete the database file or drop schema <schema> cascade, then run dbt run again)
  • Fixed model-level foreign key rendering
  • Fixed external models whose location ends in a compression extension (e.g. out.csv.gz)
  • Fixed MotherDuck options set under alternate spellings (e.g. MOTHERDUCK_TOKEN, token) being re-issued as SET statements
  • Fixed database name derivation for file names with more than one dot, matching DuckDB
  • Fixed quoting of contract column names in the insert column list
  • Fixed sql_header on models with enforced contracts
  • Fixed TypeError when creating the postgres plugin
  • Added Python 3.14 to the CI matrix
  • Added support for running Python models via MotherDuck Flights
Commits
  • 949ff68 Add changelog entries for 1.11.0 and 1.11.1 (#868)
  • 5d446d9 Rebuild foreign key families on rerun instead of failing (#863)
  • a993eae Infer the external format from compressed file locations (#860)
  • 2340eeb Pin DuckDB 1.5.5 for the Buena Vista tests (#867)
  • 89d8ae9 Run Python models on MotherDuck Flights (#840)
  • 7be353f Authenticate the fsspec GitHub filesystem test to avoid API rate limits (#862)
  • 123a75c Expand DuckDB 2.0 pre-release coverage in nightly CI (#858)
  • a02d275 Remove every accepted spelling of MotherDuck options from settings (#861)
  • c48d76a Derive the database name from a dotted file name the way DuckDB does (#854)
  • a2e2c2a Quote contract column names in the insert column list (#856)
  • Additional commits viewable in compare view

Updates clickhouse-connect from 1.11.0 to 1.12.0

Release notes

Sourced from clickhouse-connect's releases.

v1.12.0

clickhouse-connect v1.12.0

Highlights

Features

  • ping() on the sync and async clients accepts an optional timeout in seconds (default 3). Closes #192.
  • New get_client(dedicated_pool=True) gives a synchronous HTTP client its own connection pool. Closing a client-owned pool now closes idle connections immediately. Closes #1121.

Performance

  • Faster Array column reads with the C extensions in all query methods. Related to #1008.
  • Faster Cython decoding of Date and Date32 columns.
  • Faster query_df reads of Map, nullable integer, nullable date, and timezone-aware nullable datetime columns with the Python codec.
  • AsyncClient.query_rows_stream reads each block in one executor call instead of one per row, so it is much faster.
  • Faster client creation with non-UTC IANA server timezones. Closes #1120.
  • Eligible SQLAlchemy Core and ORM SELECTs skip the extra LIMIT 0 metadata query for empty results. Closes #1108 and #1134.

Bug Fixes

  • Correct Date32 decoding before 1601 and in leap centuries such as 1600 and 2400.
  • Nullable(Tuple(...)) and Nullable(Point) now read and insert correctly with the Python codec, including NULLs. Closes #1102 and #1104.
  • pandas.Timestamp keeps nanoseconds in DateTime64(7..9) binds and inserts. Tuple, Nested, Map, and Variant parameters keep DateTime64 precision. Related to #429.
  • Datetime parameters whose names end in _64 no longer fail with KeyError in pyformat queries. Closes #1131.
  • Large queries are no longer form-encoded automatically, which avoids Field value too long errors. Closes #1105.
  • NumPy and pandas reads: LIMIT 0 queries return empty results, object-column rows keep the correct shape, and numeric LowCardinality columns return every row.
  • query_df with use_none=False works on Nullable(Date) and Nullable(Date32).
  • Async connection drops raise OperationalError or StreamFailureError instead of leaking aiohttp errors. Mid-stream drops on both clients report StreamFailureError and keep the original cause.
  • AsyncClient.query(context=...) applies per-call arguments, and query(context=...) runs a stored command statement.
  • Context tz_mode is preserved across all query methods.
  • Enum names with backslashes or control characters parse and insert correctly. See #1117.
  • Decimal256(S) resolves to precision 76.
  • Fixes to timezone file handling, Tuple serialization error reporting, Nullable(SimpleAggregateFunction) NULL inserts, and a C buffer crash on zero-length first reads.

Other

  • AsyncClient.raw_insert now types insert_block as an async iterable of bytes. Runtime behavior is unchanged.

Note for Python 3.14+

lz4 is no longer installed by default on Python 3.14 and later. In that case compress=True compresses inserts with zstd from the standard library. To keep using compress="lz4",install clickhouse-connect[lz4]. Nothing changes below 3.14.

Installation

pip install --upgrade clickhouse-connect

See the CHANGELOG for full details.

Changelog

Sourced from clickhouse-connect's changelog.

1.12.0, 2026-11-03

Bug Fixes

  • Fixed Date32 decoding before 1601 and in leap centuries such as 1600 and 2400. Python date results support years 1 through 9999, with out-of-range values raising ValueError. The same calendar correction applies to epoch-based DateTime64 decoding.
  • With the Python codec and extended pandas dtypes, query_df preserves Nullable(UInt64) values above 2**53 without rounding, keeps timezone-aware nullable datetime dtypes across all-NULL blocks, and reads valid Nullable(DateTime64) values beyond the nanosecond range on pandas 2.
  • Datetime parameters whose names end in _64 now retain their names in pyformat queries, fixing KeyError failures including SQLAlchemy queries with 64 datetime binds. The _64 precision hint still applies when the query uses the name without the suffix. Closes #1131.
  • The Python codec now decodes Nullable(Tuple(...)) correctly, preserving NULL tuples and non-NULL values, including nested tuples and tuple read formats. Closes #1102.
  • The Python codec now decodes Nullable(Point) columns, returning None for NULL points. Previously the decoder read the NULL map as point data and the query failed.
  • With the Rust codec, query_column_block_stream now returns unnamed Nullable(Tuple(...)) columns, including Nullable(Tuple()), as lists instead of tuples, matching the Python codec. Row results are unchanged.
  • The Python codec now inserts None into Nullable(Tuple(...)) and Nullable(Point) columns as NULL, including when nested in Array or Tuple. Previously these inserts failed with TypeError or AttributeError before reaching the server. Tuple elements keep their declared types' validation and input handling, including Decimal aliases and nullable SimpleAggregateFunction elements. Native insert headers now preserve the tuple's Nullable wrapper. Closes #1104.
  • The Python codec now inserts None into Nullable(SimpleAggregateFunction(...)) columns as NULL.
  • Tuple serialization now reports non-sequence rows with DataError and a row number instead of a raw TypeError or AttributeError, including None rows in dictionary input for a non-nullable named tuple.
  • Decimal256(S) now resolves to the supported precision of 76 instead of 79. Explicit Decimal256 type names now produce valid Native insert headers, and SQLAlchemy Decimal256 types report the correct precision.
  • Sync and async clients no longer automatically use form encoding when the final SQL exceeds 128 KiB, avoiding HTML Form Exception: Field value too long for large queries with large bound parameters. Explicit form encoding and queries with external data retain their existing limits. Closes #1105.
  • pandas.Timestamp values keep their nanoseconds when bound to a DateTime64(9) query parameter, including typed SQLAlchemy bind parameters and values wrapped in DT64Param, and when inserted as rows into DateTime64(7) through DateTime64(9) columns with the Python codec. Previously both paths truncated them to microseconds, so 2024-01-02 03:04:05.123456789 arrived as 2024-01-02 03:04:05.123456000. Python codec row inserts of a pandas.Timestamp whose sub-microsecond part rounds up, such as 03:04:05.999999999, also no longer store a value one second late in any DateTime64 column. Related to #429.
  • Server-side query parameters typed as a named Tuple, Nested, or Map now keep the sub-second precision of datetime values bound to their DateTime64 elements, and each element uses its declared timezone. Map parameters require dict_parameter_format="map". A Variant keeps precision and timezone only when its sole datetime alternative is a DateTime64. Enum labels and field names containing datetime don't count as datetime types. Variants with several datetime alternatives are unchanged.
  • Enum names that contain a backslash or a control character such as a tab now parse correctly from server type names and are escaped correctly in Native insert headers. Previously such names read back escaped, for example c\\d instead of c\d. Inserting them stored 0, which became the wrong label when 0 was a declared member and an unreadable value otherwise. See #1117.
  • The asynchronous client now raises OperationalError when the connection drops while raw_query, command, or a LIMIT 0 metadata query reads the response body, matching the synchronous client. Previously it leaked aiohttp.ClientPayloadError.
  • When the connection drops partway through a streamed query result, both sync and async clients now raise StreamFailureError: Stream failed during read (connection closed by server) and preserve the transport error as the cause. Previously, with show_clickhouse_errors=True, they could report buffered result bytes as unrecognized data found in stream: <hex> and suppress the cause. Recognizable ClickHouse errors written into the response before the drop are still reported.
  • AsyncClient.raw_insert now types insert_block as an async iterable of bytes instead of a sync generator. Async generators already worked but failed type checking. Runtime behavior is unchanged.
  • query_df and query_df_stream with use_none=False no longer raise TypeError on Nullable(Date) and Nullable(Date32), including inside arrays, tuples, maps, and LowCardinality columns. With extended dtypes (the default), NULLs return as NaT, matching use_none=True. NumPy queries with an extended-dtype context and use_none=False also support NULLs and retain datetime64[D] resolution.
  • AsyncClient.query(context=...) now applies the arguments passed with the call, such as parameters, settings, and query, on a copy of the context, matching the synchronous client. Previously the async client ignored them and ran the stored context unchanged, so concurrent calls that shared one context with different parameters all returned the stored context's result.
  • All sync and async query methods that accept a context now preserve its explicitly set tz_mode unless the call overrides it. Contexts without an explicit mode use the calling client's current default, as the sync client already did. Invalid context tz_mode assignments now raise ProgrammingError immediately.
  • query(context=...) now runs a command statement stored in the context, such as CREATE or SET, when no query argument is passed. Previously both the synchronous and asynchronous clients raised AttributeError: 'NoneType' object has no attribute 'rstrip'.
  • Unreadable timezone files and timezone directory names now follow the existing unrecognized-timezone handling. This prevents an import failure when TZ names a directory such as America and the tzdata package is installed.
  • The compiled Cython response buffer no longer segfaults when the first read from a stream is zero bytes, such as a zero-row Array, numeric, FixedString or Nullable(String) column, or an empty String value whose length byte arrived in its own chunk. Normal query results never take this path. The first chunk of a response is always more than one byte and loads the buffer. Only direct use of the buffer and datatype read APIs was affected.

Improvements

  • On Python 3.14 and later, lz4 is no longer installed by default. It publishes no wheels for Python 3.14+ free-threaded builds, CPython 3.15 or musllinux, and zstd is in the standard library from 3.14. Without lz4, compress=True compresses inserts with zstd. Query responses already use zstd because the server prefers it. Install clickhouse-connect[lz4] to use compress="lz4" on 3.14 and later. Nothing changes below 3.14.
  • Cython decoding of Date and Date32 columns is faster because Python date objects are constructed directly through the datetime C API. Results are the same as before.
  • ping() on the sync and async clients accepts an optional positive timeout in seconds, defaulting to 3 seconds when omitted or None. HTTP clients reject zero or negative values with ProgrammingError. The chDB client ignores the parameter. Closes #192.
  • Added get_client(dedicated_pool=True) for synchronous HTTP clients that need their own connection pool. Closing any client-owned pool now closes idle connections immediately and closes active connections when their responses return to the pool. Requests racing with close() can fail with OperationalError, including for existing TLS/proxy-owned pools. The async client accepts the option without effect because it already owns its connector. Closes #1121.
  • Client creation is faster with non-UTC IANA server timezones because timezone validation no longer scans the timezone database. Closes #1120.
  • query_np, query_df, query_np_stream, and query_df_stream no longer raise AttributeError for a query that ends in LIMIT 0. They now return an empty result, the same as a query that matches no rows. Related to #257. Empty results still don't include column names.
  • query_np now returns one row per result row when every column is returned as Python objects and some values are lists or tuples, for example a single Array or Tuple column. Previously numpy unpacked those values into extra dimensions, so SELECT [number, number + 1, number + 2] FROM numbers(2) came back with shape (3, 2, 1) instead of (2, 1). This also fixes a concatenation error for nested Array or Tuple results spread across multiple blocks.
  • query_np and query_df now return every row of a numeric LowCardinality column, such as LowCardinality(Int32). Previously the column was cut to the size of its dictionary, so 1000 rows with 300 distinct values came back as 300 rows, and a block with fewer rows than dictionary entries raised ValueError: iterator too short.
  • AsyncClient.query_rows_stream now reads each result block in the executor once and yields its rows on the event loop. Previously it made one executor call per row, so streaming rows asynchronously was far slower than the synchronous query_rows_stream.
  • The Python codec reads Map, nullable integer, nullable date, and timezone-aware nullable datetime columns faster in query_df by avoiding per-row pandas conversions.
  • With the C extensions, the Python codec reads Array columns faster in all query methods. Related to #1008.
  • Eligible compiled SQLAlchemy Core and ORM SELECT queries now skip the second LIMIT 0 metadata query for empty results and preserve result keys. A projection qualifies when it has a fixed column shape with unique compiled names and every result column uses a result processor that does not read the server type code. This covers SQLAlchemy's generic types whose processors depend only on dialect flags, such as String, Boolean, Numeric, Float, Enum, and types that inherit the default TypeEngine processor, the driver's reflected ChSqlaType types, and TypeDecorator wrappers over those, including nested wrappers, with_variant, and load_dialect_impl. The synthesized DB-API descriptions report None for type_code and null_ok. Plain DB-API and textual queries, raw SQL projections or modifiers, server-expanded columns, custom result_processor overrides, Enum subclasses, JSON, rewritten statements, and cursor execute wrappers retain the LIMIT 0 metadata fallback. Closes #1108 and #1134.
Commits
  • f04e7c1 release prep for v1.12.0 (#1145)
  • cbd11b4 Fix extended Date32 decoding and speed up Cython date conversion (#1142)
  • 96ef200 Fix crash reading an empty Array column with the C buffer (#1140)
  • 8c5c12f Speed up Array column reads with a Cython row builder (#1138)
  • 5520216 Make lz4 optional on Python 3.14+ (#1139)
  • 6f24bb8 Add optional timeout parameter to ping() (#1137)
  • 93408a0 Keep DateTime64 precision in pandas.Timestamp binds and inserts and in Tuple,...
  • f92d24d Skip empty SQLAlchemy metadata probes for decorators and generic types (#1135)
  • a5a68cf Decode backslash escapes in Enum names from server type names (#1117)
  • 7df5b4c Speed up Map, nullable DateTime/Date and nullable Int columns in query_df (#1...
  • Additional commits viewable in compare view

Updates dbt-bigquery from 1.12.1 to 1.12.3

Commits

Updates dbt-snowflake from 1.12.3 to 1.12.5

Commits

Updates pyarrow from 26.0.0 to 26.0.1

Release notes

Sourced from pyarrow's releases.

Apache Arrow 26.0.1

Release Notes URL: https://arrow.apache.org/release/26.0.1.html

Apache Arrow 26.0.1 RC1

Release Notes: Release Candidate: 26.0.1 RC1

Commits
  • 9e5d697 MINOR: [Release] Update versions for 26.0.1
  • 905f17c MINOR: [Release] Update .deb/.rpm changelogs for 26.0.1
  • Description has been truncated

Bumps the python-minor-and-patch group with 11 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [typer](https://github.com/fastapi/typer) | `0.27.3` | `0.29.1` |
| [dbt-core](https://github.com/dbt-labs/dbt-core) | `1.12.6` | `1.12.7` |
| [dbt-duckdb](https://github.com/duckdb/dbt-duckdb) | `1.11.0` | `1.11.1` |
| [clickhouse-connect](https://github.com/ClickHouse/clickhouse-connect) | `1.11.0` | `1.12.0` |
| [dbt-bigquery](https://github.com/dbt-labs/dbt-adapters) | `1.12.1` | `1.12.3` |
| [dbt-snowflake](https://github.com/dbt-labs/dbt-adapters) | `1.12.3` | `1.12.5` |
| [pyarrow](https://github.com/apache/arrow) | `26.0.0` | `26.0.1` |
| [dlt](https://github.com/dlt-hub/dlt) | `1.31.0` | `1.32.0` |
| [airbyte-cdk](https://github.com/airbytehq/airbyte-python-cdk) | `7.38.0` | `7.48.0` |
| [pytest](https://github.com/pytest-dev/pytest) | `9.1.1` | `9.2.0` |
| [ruff](https://github.com/astral-sh/ruff) | `0.17.1` | `0.17.5` |



Updates `typer` from 0.27.3 to 0.29.1
- [Release notes](https://github.com/fastapi/typer/releases)
- [Changelog](https://github.com/fastapi/typer/blob/master/docs/release-notes.md)
- [Commits](fastapi/typer@0.27.3...0.29.1)

Updates `dbt-core` from 1.12.6 to 1.12.7
- [Release notes](https://github.com/dbt-labs/dbt-core/releases)
- [Changelog](https://github.com/dbt-labs/dbt/blob/v1.12.7/CHANGELOG.md)
- [Commits](dbt-labs/dbt@v1.12.6...v1.12.7)

Updates `dbt-duckdb` from 1.11.0 to 1.11.1
- [Release notes](https://github.com/duckdb/dbt-duckdb/releases)
- [Changelog](https://github.com/duckdb/dbt-duckdb/blob/main/CHANGELOG.md)
- [Commits](duckdb/dbt-duckdb@1.11.0...1.11.1)

Updates `clickhouse-connect` from 1.11.0 to 1.12.0
- [Release notes](https://github.com/ClickHouse/clickhouse-connect/releases)
- [Changelog](https://github.com/ClickHouse/clickhouse-connect/blob/main/CHANGELOG.md)
- [Commits](ClickHouse/clickhouse-connect@v1.11.0...v1.12.0)

Updates `dbt-bigquery` from 1.12.1 to 1.12.3
- [Release notes](https://github.com/dbt-labs/dbt-adapters/releases)
- [Changelog](https://github.com/dbt-labs/dbt-adapters/blob/main/CHANGELOG.md)
- [Commits](https://github.com/dbt-labs/dbt-adapters/commits)

Updates `dbt-snowflake` from 1.12.3 to 1.12.5
- [Release notes](https://github.com/dbt-labs/dbt-adapters/releases)
- [Changelog](https://github.com/dbt-labs/dbt-adapters/blob/main/CHANGELOG.md)
- [Commits](https://github.com/dbt-labs/dbt-adapters/commits)

Updates `pyarrow` from 26.0.0 to 26.0.1
- [Release notes](https://github.com/apache/arrow/releases)
- [Commits](apache/arrow@apache-arrow-26.0.0...apache-arrow-26.0.1)

Updates `dlt` from 1.31.0 to 1.32.0
- [Release notes](https://github.com/dlt-hub/dlt/releases)
- [Commits](dlt-hub/dlt@1.31.0...1.32.0)

Updates `airbyte-cdk` from 7.38.0 to 7.48.0
- [Release notes](https://github.com/airbytehq/airbyte-python-cdk/releases)
- [Changelog](https://github.com/airbytehq/airbyte-python-cdk/blob/main/CHANGELOG.md)
- [Commits](airbytehq/airbyte-python-cdk@v7.38.0...v7.48.0)

Updates `pytest` from 9.1.1 to 9.2.0
- [Release notes](https://github.com/pytest-dev/pytest/releases)
- [Changelog](https://github.com/pytest-dev/pytest/blob/main/CHANGELOG.rst)
- [Commits](pytest-dev/pytest@9.1.1...9.2.0)

Updates `ruff` from 0.17.1 to 0.17.5
- [Release notes](https://github.com/astral-sh/ruff/releases)
- [Changelog](https://github.com/astral-sh/ruff/blob/main/CHANGELOG.md)
- [Commits](astral-sh/ruff@0.17.1...0.17.5)

---
updated-dependencies:
- dependency-name: typer
  dependency-version: 0.29.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: python-minor-and-patch
- dependency-name: dbt-core
  dependency-version: 1.12.7
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: python-minor-and-patch
- dependency-name: dbt-duckdb
  dependency-version: 1.11.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: python-minor-and-patch
- dependency-name: clickhouse-connect
  dependency-version: 1.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: python-minor-and-patch
- dependency-name: dbt-bigquery
  dependency-version: 1.12.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: python-minor-and-patch
- dependency-name: dbt-snowflake
  dependency-version: 1.12.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: python-minor-and-patch
- dependency-name: pyarrow
  dependency-version: 26.0.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: python-minor-and-patch
- dependency-name: dlt
  dependency-version: 1.32.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: python-minor-and-patch
- dependency-name: airbyte-cdk
  dependency-version: 7.48.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: python-minor-and-patch
- dependency-name: pytest
  dependency-version: 9.2.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: python-minor-and-patch
- dependency-name: ruff
  dependency-version: 0.17.5
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: python-minor-and-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file python:uv Pull requests that update python:uv code labels Nov 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file python:uv Pull requests that update python:uv code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants