Skip to content

Bump sqlparse to 0.6.0 in dbt-feldera - #6987

Open
mythical-fred-ops[bot] wants to merge 1 commit into
mainfrom
fred/security-updates-2026-08-28
Open

Bump sqlparse to 0.6.0 in dbt-feldera#6987
mythical-fred-ops[bot] wants to merge 1 commit into
mainfrom
fred/security-updates-2026-08-28

Conversation

@mythical-fred-ops

Copy link
Copy Markdown

Clears the sqlparse advisories in python/dbt-feldera/uv.lock.

Alert GHSA Package Severity Old → new Rung
366 GHSA-prg7-hcfm-mfcr sqlparse high 0.5.4 → 0.6.0 1 (lockfile only)
365 GHSA-pwgv-4x5q-6m9f sqlparse high 0.5.4 → 0.6.0 1 (lockfile only)
364 GHSA-f2ff-p2ww-7p4p sqlparse high 0.5.4 → 0.6.0 1 (lockfile only)
363 GHSA-3496-9g83-7v6x sqlparse medium 0.5.4 → 0.6.0 1 (lockfile only)

dbt-core 1.11.7 requires sqlparse>=0.5.0,<0.5.5, so the lock also moves
dbt-core to 1.11.14 — the earliest 1.11 release that allows 0.6.0. Both
versions already satisfy dbt-core~=1.11 in pyproject.toml; no manifest
change was needed.

Validation

Check Result
uv lock --check consistent
sqlparse resolved in uv.lock 0.6.0
uv run pytest -m "not integration" 129 passed, 254 subtests passed
pre-commit run --files python/dbt-feldera/uv.lock passed

sqlparse 0.5.4 is affected by four advisories (GHSA-prg7-hcfm-mfcr,
GHSA-pwgv-4x5q-6m9f, GHSA-f2ff-p2ww-7p4p, GHSA-3496-9g83-7v6x), all first
fixed in 0.6.0. dbt-core 1.11.7 caps sqlparse below 0.5.5, so the lock also
moves dbt-core to 1.11.14, the earliest release in the 1.11 line whose
requirement (sqlparse >=0.5.5,<0.7.0) admits the fix. Both bumps stay inside
the ranges pyproject.toml already declares, so no manifest change is needed.

Signed-off-by: mythical-fred-ops[bot] <268516273+mythical-fred-ops[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants