[Bug] dbt invocations at version 1.10.0 return ModuleNotFoundError

[katieclaiborne-duet]

Is this a new bug in dbt-core?

• I believe this is a new bug in dbt-core
• I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior

After the version 1.10.0 release, our GitHub Actions workflow runs, which begin with a dbt deps command, started failing with the error below:

18:03:19  Running with dbt=1.10.0
18:03:19  Encountered an error:
No module named 'jsonschema._keywords'
18:03:19  Traceback (most recent call last):
  File "/home/runner/.local/lib/python3.12/site-packages/dbt/cli/requires.py", line 161, in wrapper
    result, success = func(*args, **kwargs)
                      ^^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/.local/lib/python3.12/site-packages/dbt/cli/requires.py", line 111, in wrapper
    return func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/.local/lib/python3.12/site-packages/dbt/cli/requires.py", line 237, in wrapper
    return func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/.local/lib/python3.12/site-packages/dbt/cli/requires.py", line [27](https://github.com/Duet-Technologies/dbt/actions/runs/15688316509/job/44197036530?pr=1015#step:9:28)2, in wrapper
    project = load_project(
              ^^^^^^^^^^^^^
  File "/home/runner/.local/lib/python3.12/site-packages/dbt/config/runtime.py", line 58, in load_project
    project = Project.from_project_root(
              ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/.local/lib/python3.12/site-packages/dbt/config/project.py", line 768, in from_project_root
    partial = PartialProject.from_project_root(
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/.local/lib/python3.12/site-packages/dbt/config/project.py", line 579, in from_project_root
    project_dict = load_raw_project(project_root, validate=validate)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/.local/lib/python3.12/site-packages/dbt/config/project.py", line 209, in load_raw_project
    from dbt.jsonschemas import jsonschema_validate, project_schema
  File "/home/runner/.local/lib/python3.12/site-packages/dbt/jsonschemas.py", line 10, in <module>
    from jsonschema._keywords import type as type_rule
ModuleNotFoundError: No module named 'jsonschema._keywords'

The workflow seems to be installing a version of jsonschema prior to a _keywords rename (python-jsonschema/jsonschema@9313230, released in 4.19.1; see "Relevant log output" section below).

Is it possible that additional dependency version updates are required for dbt version 1.10.0?

Expected Behavior

Previously, the workflow ran on version 1.9.8 without issue.

Steps To Reproduce

1. In a virtual environment, install dbt-core and dbt-bigquery.
2. Install an earlier version of jsonschema.

pip install jsonschema==4.10.3

2. Execute dbt deps
3. Observe ModuleNotFoundError

Relevant log output

Requirement already satisfied: jsonschema<5.0,>=4.0 in /usr/lib/python3/dist-packages (from dbt-common<2.0,>=1.10->dbt-bigquery~=1.9.0->-r requirements.txt (line 1)) (4.10.3)

Environment

- OS: ubuntu-24.04
- Python: 3.12.3
- dbt: 1.10.0

Which database adapter are you using with dbt?

BigQuery

Additional Context

GitHub Actions runner image info:

Runner Image
  Image: ubuntu-24.04
  Version: 20250602.3.0
  Included Software: https://github.com/actions/runner-images/blob/ubuntu24/20250602.3/images/ubuntu/Ubuntu2404-Readme.md
  Image Release: https://github.com/actions/runner-images/releases/tag/ubuntu24%2F20250602.3

[zgcalebp]

We are seeing this exact same issue now causing significant outages in production pipelines.

[NickBenthem-Afresh]

We are also affected.

[foundinblank]

Same here!

[poloaraujo]

We're seeing this issue too

[QMalcolm]

TL;DR

upgrade your jsonschema version with pip install "jsonschema>=4.19.1"

Longer version

We've identified the issue. The issue is that the submodule we're relying on, _keywords was introduced until jsonschema 4.19.1 but we allow for jsonschema>=4.0,<5. In environments with a jsonchema version <4.19.1 you will receive this error. We'll put out a fix in 1.10.1 which will be to require jsonschema>=4.19.1. Until then the work around is to upgrade your jsonschema version manually via pip install "jsonschema>=4.19.1"

[QMalcolm]

@katieclaiborne-duet Thank you for creating this issue and bringing it to our attention ❤ Also, so sorry that this happened 😞

[QMalcolm]

Also sorry that my first comment re-states much of what was identified in the original issue 🙃 This bug was brought to my attention through separate means without the debug information you had already provided