Skip to content

Bump the pip-dependency-updates group across 3 directories with 2 updates#66880

Closed
dependabot[bot] wants to merge 5 commits into
v3-2-testfrom
dependabot/pip/airflow-core/v3-2-test/pip-dependency-updates-1a800ef2ca
Closed

Bump the pip-dependency-updates group across 3 directories with 2 updates#66880
dependabot[bot] wants to merge 5 commits into
v3-2-testfrom
dependabot/pip/airflow-core/v3-2-test/pip-dependency-updates-1a800ef2ca

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github May 13, 2026 •
edited
Loading

Updates the requirements on aiosqlite and datamodel-code-generator to permit the latest version.
Updates aiosqlite to 0.22.1

Changelog

Sourced from aiosqlite's changelog.

v0.22.1

Bug fix release

NOTE: Starting with v0.22.0, the aiosqlite.Connection object no longer inherits from threading.Thread. If not using aiosqlite as a context manager, clients must await connection.close() or call connection.stop() to ensure the helper thread is completed and terminated correctly. A ResourceWarning will be emitted for any connection that is garbage collected without being closed or stopped.

  • Added synchronous stop() method to aiosqlite.Connection to enable safe cleanup and termination of the background thread without dependence on having an active event loop (#370)
$ git shortlog -s v0.22.0...v0.22.1
     2	Amethyst Reese

v0.22.0

Feature release

  • Support set_authorizer query access controls (#349)
  • Wait for transaction queue to complete when closing connection (#305)
  • Emit warning when connection goes out of scope without being closed (#355)
  • Remove dependency on typing_extensions (#365)
$ git shortlog -s v0.21.0...v0.22.0
     1	Alec Berryman
     1	Amethyst Reese
     1	David Andreoletti
     1	Markus Heidelberg
     1	beerpsi
    19	dependabot[bot]

v0.21.0

Maintenance release

  • Fix: close connection correctly when BaseException raised in connection (#317)
  • Metadata improvements

... (truncated)

Commits

Updates datamodel-code-generator from 0.33.0 to 0.57.0

Release notes

Sourced from datamodel-code-generator's releases.

0.57.0

Breaking Changes

Code Generation Changes

  • --use-default no longer makes required fields nullable - Previously, --use-default turned required fields into optional nullable fields (e.g., status: str | None = 'active'). Now required fields keep their original non-nullable type and just get the default value rendered (e.g., status: str = 'active'). Users whose downstream code depends on these fields being Optional/nullable will need to update. (#3054)
  • Required model-ref fields no longer render defaults without --use-default - Previously, required fields referencing models (e.g., shipping_address: Address) inconsistently rendered defaults with validate_default=True while scalar required fields did not. Now all required fields consistently omit defaults unless --use-default is passed. Users who relied on the previous behavior where model-ref required fields had defaults rendered will see those defaults removed. (#3054)

Custom Template Update Required

  • Built-in Jinja2 templates now use field.use_default_with_required - The built-in templates for BaseModel, dataclass, pydantic_v2/dataclass, and msgspec were updated to check field.use_default_with_required alongside field.required when deciding whether to render defaults. Custom templates that replicate the old default-rendering logic (e.g., {%- if not field.required %}) will still work but won't support the new --use-default behavior for required fields. To get the updated behavior, custom templates should change conditions like not field.required to (not field.required or field.use_default_with_required). (#3054)

What's Changed

... (truncated)

Changelog

Sourced from datamodel-code-generator's changelog.

0.57.0 - 2026-05-07

Breaking Changes

Code Generation Changes

  • --use-default no longer makes required fields nullable - Previously, --use-default turned required fields into optional nullable fields (e.g., status: str | None = 'active'). Now required fields keep their original non-nullable type and just get the default value rendered (e.g., status: str = 'active'). Users whose downstream code depends on these fields being Optional/nullable will need to update. (#3054)
  • Required model-ref fields no longer render defaults without --use-default - Previously, required fields referencing models (e.g., shipping_address: Address) inconsistently rendered defaults with validate_default=True while scalar required fields did not. Now all required fields consistently omit defaults unless --use-default is passed. Users who relied on the previous behavior where model-ref required fields had defaults rendered will see those defaults removed. (#3054)

Custom Template Update Required

  • Built-in Jinja2 templates now use field.use_default_with_required - The built-in templates for BaseModel, dataclass, pydantic_v2/dataclass, and msgspec were updated to check field.use_default_with_required alongside field.required when deciding whether to render defaults. Custom templates that replicate the old default-rendering logic (e.g., {%- if not field.required %}) will still work but won't support the new --use-default behavior for required fields. To get the updated behavior, custom templates should change conditions like not field.required to (not field.required or field.use_default_with_required). (#3054)

What's Changed

New Contributors

Full Changelog: koxudaxi/datamodel-code-generator@0.56.1...0.57.0

0.56.1 - 2026-04-16

What's Changed

... (truncated)

Commits

Updates datamodel-code-generator from 0.33.0 to 0.57.0

Release notes

Sourced from datamodel-code-generator's releases.

0.57.0

Breaking Changes

Code Generation Changes

  • --use-default no longer makes required fields nullable - Previously, --use-default turned required fields into optional nullable fields (e.g., status: str | None = 'active'). Now required fields keep their original non-nullable type and just get the default value rendered (e.g., status: str = 'active'). Users whose downstream code depends on these fields being Optional/nullable will need to update. (#3054)
  • Required model-ref fields no longer render defaults without --use-default - Previously, required fields referencing models (e.g., shipping_address: Address) inconsistently rendered defaults with validate_default=True while scalar required fields did not. Now all required fields consistently omit defaults unless --use-default is passed. Users who relied on the previous behavior where model-ref required fields had defaults rendered will see those defaults removed. (#3054)

Custom Template Update Required

  • Built-in Jinja2 templates now use field.use_default_with_required - The built-in templates for BaseModel, dataclass, pydantic_v2/dataclass, and msgspec were updated to check field.use_default_with_required alongside field.required when deciding whether to render defaults. Custom templates that replicate the old default-rendering logic (e.g., {%- if not field.required %}) will still work but won't support the new --use-default behavior for required fields. To get the updated behavior, custom templates should change conditions like not field.required to (not field.required or field.use_default_with_required). (#3054)

What's Changed

... (truncated)

Changelog

Sourced from datamodel-code-generator's changelog.

0.57.0 - 2026-05-07

Breaking Changes

Code Generation Changes

  • --use-default no longer makes required fields nullable - Previously, --use-default turned required fields into optional nullable fields (e.g., status: str | None = 'active'). Now required fields keep their original non-nullable type and just get the default value rendered (e.g., status: str = 'active'). Users whose downstream code depends on these fields being Optional/nullable will need to update. (#3054)
  • Required model-ref fields no longer render defaults without --use-default - Previously, required fields referencing models (e.g., shipping_address: Address) inconsistently rendered defaults with validate_default=True while scalar required fields did not. Now all required fields consistently omit defaults unless --use-default is passed. Users who relied on the previous behavior where model-ref required fields had defaults rendered will see those defaults removed. (#3054)

Custom Template Update Required

  • Built-in Jinja2 templates now use field.use_default_with_required - The built-in templates for BaseModel, dataclass, pydantic_v2/dataclass, and msgspec were updated to check field.use_default_with_required alongside field.required when deciding whether to render defaults. Custom templates that replicate the old default-rendering logic (e.g., {%- if not field.required %}) will still work but won't support the new --use-default behavior for required fields. To get the updated behavior, custom templates should change conditions like not field.required to (not field.required or field.use_default_with_required). (#3054)

What's Changed

New Contributors

Full Changelog: koxudaxi/datamodel-code-generator@0.56.1...0.57.0

0.56.1 - 2026-04-16

What's Changed

... (truncated)

Commits

Updates datamodel-code-generator from 0.33.0 to 0.57.0

Release notes

Sourced from datamodel-code-generator's releases.

0.57.0

Breaking Changes

Code Generation Changes

  • --use-default no longer makes required fields nullable - Previously, --use-default turned required fields into optional nullable fields (e.g., status: str | None = 'active'). Now required fields keep their original non-nullable type and just get the default value rendered (e.g., status: str = 'active'). Users whose downstream code depends on these fields being Optional/nullable will need to update. (#3054)
  • Required model-ref fields no longer render defaults without --use-default - Previously, required fields referencing models (e.g., shipping_address: Address) inconsistently rendered defaults with validate_default=True while scalar required fields did not. Now all required fields consistently omit defaults unless --use-default is passed. Users who relied on the previous behavior where model-ref required fields had defaults rendered will see those defaults removed. (#3054)

Custom Template Update Required

  • Built-in Jinja2 templates now use field.use_default_with_required - The built-in templates for BaseModel, dataclass, pydantic_v2/dataclass, and msgspec were updated to check field.use_default_with_required alongside field.required when deciding whether to render defaults. Custom templates that replicate the old default-rendering logic (e.g., {%- if not field.required %}) will still work but won't support the new --use-default behavior for required fields. To get the updated behavior, custom templates should change conditions like not field.required to (not field.required or field.use_default_with_required). (#3054)

What's Changed

... (truncated)

Changelog

Sourced from datamodel-code-generator's changelog.

0.57.0 - 2026-05-07

Breaking Changes

Code Generation Changes

  • --use-default no longer makes required fields nullable - Previously, --use-default turned required fields into optional nullable fields (e.g., status: str | None = 'active'). Now required fields keep their original non-nullable type and just get the default value rendered (e.g., status: str = 'active'). Users whose downstream code depends on these fields being Optional/nullable will need to update. (#3054)
  • Required model-ref fields no longer render defaults without --use-default - Previously, required fields referencing models (e.g., shipping_address: Address) inconsistently rendered defaults with validate_default=True while scalar required fields did not. Now all required fields consistently omit defaults unless --use-default is passed. Users who relied on the previous behavior where model-ref required fields had defaults rendered will see those defaults removed. (#3054)

Custom Template Update Required

  • Built-in Jinja2 templates now use field.use_default_with_required - The built-in templates for BaseModel, dataclass, pydantic_v2/dataclass, and msgspec were updated to check field.use_default_with_required alongside field.required when deciding whether to render defaults. Custom templates that replicate the old default-rendering logic (e.g., {%- if not field.required %}) will still work but won't support the new --use-default behavior for required fields. To get the updated behavior, custom templates should change conditions like not field.required to (not field.required or field.use_default_with_required). (#3054)

What's Changed

New Contributors

Full Changelog: koxudaxi/datamodel-code-generator@0.56.1...0.57.0

0.56.1 - 2026-04-16

What's Changed

... (truncated)

Commits

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file python Pull requests that update Python code labels May 13, 2026
@dependabot dependabot Bot added python Pull requests that update Python code dependencies Pull requests that update a dependency file labels May 13, 2026
@potiuk
Copy link
Copy Markdown
Member

potiuk commented May 13, 2026

@dependabot recreate

@dependabot dependabot Bot force-pushed the dependabot/pip/airflow-core/v3-2-test/pip-dependency-updates-1a800ef2ca branch 5 times, most recently from adc2d15 to d1aa822 Compare May 20, 2026 01:55
@vatsrahul1001 vatsrahul1001 force-pushed the dependabot/pip/airflow-core/v3-2-test/pip-dependency-updates-1a800ef2ca branch from d1aa822 to d8c7cd1 Compare May 20, 2026 06:24
vatsrahul1001 and others added 5 commits May 21, 2026 08:59
@vatsrahul1001 @namratachaudhary
Fix OTel timer metrics using Gauge instead of Histogram (#64207) (#66865
b29f8e2 
)

* Fix OTel timer metrics using Gauge instead of Histogram

* Use ExponentialBucketHistogramAggregation for timing metrics

* Use public API import path for ExponentialBucketHistogramAggregation and fix histogram map isolation

(cherry picked from commit b2dadd2)

Co-authored-by: namratachaudhary <namratachaudhary@users.noreply.github.com>
@pierrejeambrun @imrichardwu
@ferruzzi @vatsrahul1001
Add name fields to SDK deadline alerts (#64926) (#65601)
faf0108 
* Add deadlines support with name and description fields in alerts and UI

* Add 'viewAll' label to deadlineStatus in dag.json

* Refactor deadlineAlerts referenceType structure

* Refine deadline alert translations in dag.json

Updated deadline alert messages for clarity and consistency.

* Add completion rule text for deadline alerts in UI

* Remove duplicate completionRule entry in deadlineAlerts

* Remove alert description from DeadlineAlert and related models

* Enhance deadline handling: return name updates alongside UUID mapping in SerializedDagModel

* Add alert_id field to DeadlineResponse and update tests for alert handling

* Remove DEADLINES option from MenuItem enum

* Update airflow-core/src/airflow/serialization/encoders.py



---------


(cherry picked from commit e9d1066)

Co-authored-by: Richard Wu <richard9@ualberta.ca>
Co-authored-by: D. Ferruzzi <ferruzzi@amazon.com>
@github-actions @Dev-iL @vatsrahul1001
[v3-2-test] Allow accessing a TaskGroup's members via [] (#64430) (#…
39604c8 
…65707)

(cherry picked from commit aa54031)

Co-authored-by: Dev-iL <6509619+Dev-iL@users.noreply.github.com>
@potiuk @vatsrahul1001
[v3-2-test] Skip test_schedule_tis_start_trigger pending #55068 backp…
899fcc3 
…ort decision (#66315)

The `start_from_trigger` deferred-at-schedule path is commented out
on v3-2-test (disabled in 91e1029 as a TODO) and was only
re-enabled on main by #55068, which landed one day after the v3-2
branch was cut. The test asserts the feature works and fails on
v3-2-test CI.

Skip the test on the 3.2 line and link the tracking issue from both
the test skip-reason and the disabled production-code site so the
follow-up isn't lost. Decision (backport #55068 or formally drop
the feature on 3.2) is tracked in #66307.
@dependabot @vatsrahul1001
Bump the pip-dependency-updates group across 3 directories with 2 upd…
1540ee0 
…ates

Updates the requirements on [aiosqlite](https://github.com/omnilib/aiosqlite) and [datamodel-code-generator](https://github.com/koxudaxi/datamodel-code-generator) to permit the latest version.

Updates `aiosqlite` to 0.22.1
- [Changelog](https://github.com/omnilib/aiosqlite/blob/main/CHANGELOG.md)
- [Commits](omnilib/aiosqlite@v0.20.0...v0.22.1)

Updates `datamodel-code-generator` from 0.33.0 to 0.57.0
- [Release notes](https://github.com/koxudaxi/datamodel-code-generator/releases)
- [Changelog](https://github.com/koxudaxi/datamodel-code-generator/blob/main/CHANGELOG.md)
- [Commits](koxudaxi/datamodel-code-generator@0.33.0...0.57.0)

Updates `datamodel-code-generator` from 0.33.0 to 0.57.0
- [Release notes](https://github.com/koxudaxi/datamodel-code-generator/releases)
- [Changelog](https://github.com/koxudaxi/datamodel-code-generator/blob/main/CHANGELOG.md)
- [Commits](koxudaxi/datamodel-code-generator@0.33.0...0.57.0)

Updates `datamodel-code-generator` from 0.33.0 to 0.57.0
- [Release notes](https://github.com/koxudaxi/datamodel-code-generator/releases)
- [Changelog](https://github.com/koxudaxi/datamodel-code-generator/blob/main/CHANGELOG.md)
- [Commits](koxudaxi/datamodel-code-generator@0.33.0...0.57.0)

Updates `datamodel-code-generator` from 0.33.0 to 0.57.0
- [Release notes](https://github.com/koxudaxi/datamodel-code-generator/releases)
- [Changelog](https://github.com/koxudaxi/datamodel-code-generator/blob/main/CHANGELOG.md)
- [Commits](koxudaxi/datamodel-code-generator@0.33.0...0.57.0)

---
updated-dependencies:
- dependency-name: aiosqlite
  dependency-version: 0.22.1
  dependency-type: direct:production
  dependency-group: pip-dependency-updates
- dependency-name: datamodel-code-generator
  dependency-version: 0.57.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: pip-dependency-updates
- dependency-name: datamodel-code-generator
  dependency-version: 0.57.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: pip-dependency-updates
- dependency-name: datamodel-code-generator
  dependency-version: 0.57.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: pip-dependency-updates
- dependency-name: datamodel-code-generator
  dependency-version: 0.57.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: pip-dependency-updates
...

Signed-off-by: dependabot[bot] <support@github.com>
@vatsrahul1001 vatsrahul1001 force-pushed the dependabot/pip/airflow-core/v3-2-test/pip-dependency-updates-1a800ef2ca branch from d8c7cd1 to 1540ee0 Compare May 21, 2026 03:30
@dependabot @github
Copy link
Copy Markdown
Contributor Author

dependabot Bot commented on behalf of github May 25, 2026

Looks like these dependencies are updatable in another way, so this is no longer needed.

@dependabot dependabot Bot closed this May 25, 2026
@dependabot dependabot Bot deleted the dependabot/pip/airflow-core/v3-2-test/pip-dependency-updates-1a800ef2ca branch May 25, 2026 23:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@ashb ashb Awaiting requested review from ashb ashb is a code owner

@kaxil kaxil Awaiting requested review from kaxil kaxil is a code owner

@amoghrajesh amoghrajesh Awaiting requested review from amoghrajesh amoghrajesh is a code owner

@bugraoz93 bugraoz93 Awaiting requested review from bugraoz93 bugraoz93 is a code owner

@potiuk potiuk Awaiting requested review from potiuk potiuk is a code owner

@dheerajturaga dheerajturaga Awaiting requested review from dheerajturaga dheerajturaga is a code owner

@jscheffl jscheffl Awaiting requested review from jscheffl

@vincbeck vincbeck Awaiting requested review from vincbeck

@shahar1 shahar1 Awaiting requested review from shahar1

@jedcunningham jedcunningham Awaiting requested review from jedcunningham

@jason810496 jason810496 Awaiting requested review from jason810496 jason810496 is a code owner

@choo121600 choo121600 Awaiting requested review from choo121600 choo121600 is a code owner

@ephraimbuddy ephraimbuddy Awaiting requested review from ephraimbuddy ephraimbuddy is a code owner

@gopidesupavan gopidesupavan Awaiting requested review from gopidesupavan

@pierrejeambrun pierrejeambrun Awaiting requested review from pierrejeambrun pierrejeambrun is a code owner

@bbovenzi bbovenzi Awaiting requested review from bbovenzi bbovenzi is a code owner

@hussein-awala hussein-awala Awaiting requested review from hussein-awala

@vatsrahul1001 vatsrahul1001 Awaiting requested review from vatsrahul1001 vatsrahul1001 is a code owner

@RNHTTR RNHTTR Awaiting requested review from RNHTTR

@josh-fell josh-fell Awaiting requested review from josh-fell

@Fokko Fokko Awaiting requested review from Fokko

@o-nikolas o-nikolas Awaiting requested review from o-nikolas

@dstandish dstandish Awaiting requested review from dstandish

@uranusjr uranusjr Awaiting requested review from uranusjr

@Lee-W Lee-W Awaiting requested review from Lee-W

@guan404ming guan404ming Awaiting requested review from guan404ming guan404ming is a code owner

@mobuchowski mobuchowski Awaiting requested review from mobuchowski

@romsharon98 romsharon98 Awaiting requested review from romsharon98

@ryanahamilton ryanahamilton Awaiting requested review from ryanahamilton ryanahamilton is a code owner

@shubhamraj-git shubhamraj-git Awaiting requested review from shubhamraj-git shubhamraj-git is a code owner

@rawwar rawwar Awaiting requested review from rawwar rawwar is a code owner

@bolkedebruin bolkedebruin Awaiting requested review from bolkedebruin bolkedebruin is a code owner

@XD-DENG XD-DENG Awaiting requested review from XD-DENG XD-DENG is a code owner

Assignees

No one assigned

Labels

area:airflow-ctl area:task-sdk dependencies Pull requests that update a dependency file python Pull requests that update Python code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@potiuk @vatsrahul1001 @pierrejeambrun