Skip to content

build(deps): bump pydantic-core from 2.41.5 to 2.42.0 in /misc/dbt-materialize in the simple group across 1 directory#35710

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/pip/misc/dbt-materialize/simple-04b90f59bb
Open

build(deps): bump pydantic-core from 2.41.5 to 2.42.0 in /misc/dbt-materialize in the simple group across 1 directory#35710
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/pip/misc/dbt-materialize/simple-04b90f59bb

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot bot commented on behalf of github Mar 27, 2026

Bumps the simple group with 1 update in the /misc/dbt-materialize directory: pydantic-core.

Updates pydantic-core from 2.41.5 to 2.42.0

Commits

@dependabot dependabot bot added the A-dependencies Area: dependency upgrades label Mar 27, 2026
@dependabot dependabot bot requested a review from a team as a code owner March 27, 2026 02:46
@github-actions
Copy link
Copy Markdown
Contributor

Thanks for opening this PR! Here are a few tips to help make the review process smooth for everyone.

PR title guidelines

  • Use imperative mood: "Fix X" not "Fixed X" or "Fixes X"
  • Be specific: "Fix panic in catalog sync when controller restarts" not "Fix bug" or "Update catalog code"
  • Prefix with area if helpful: compute: , storage: , adapter: , sql:

Pre-merge checklist

  • The PR title is descriptive and will make sense in the git log.
  • This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
  • If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.
  • This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
  • If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
  • If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).

@dependabot dependabot bot changed the title build(deps): bump pydantic-core from 2.41.5 to 2.42.0 in /misc/dbt-materialize in the simple group build(deps): bump pydantic-core from 2.41.5 to 2.42.0 in /misc/dbt-materialize in the simple group across 1 directory Mar 27, 2026
@dependabot dependabot bot force-pushed the dependabot/pip/misc/dbt-materialize/simple-04b90f59bb branch 4 times, most recently from 2563f9b to bc7a06c Compare March 31, 2026 02:46
Bumps the simple group in /misc/dbt-materialize with 1 update: [pydantic-core](https://github.com/pydantic/pydantic-core).


Updates `pydantic-core` from 2.41.5 to 2.42.0
- [Release notes](https://github.com/pydantic/pydantic-core/releases)
- [Commits](https://github.com/pydantic/pydantic-core/commits)

---
updated-dependencies:
- dependency-name: pydantic-core
  dependency-version: 2.42.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: simple
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/pip/misc/dbt-materialize/simple-04b90f59bb branch from bc7a06c to 753853a Compare April 1, 2026 02:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-dependencies Area: dependency upgrades

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants