chore(deps): dependency review for v0.1.11 (replaces #161-#168) - #180
Merged
Conversation
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
Replaces the eight Dependabot PRs (#161-#168), all of which targeted main and are now closed. Carries forward only the four with real reach; pytest, mkdocs-material and syrupy were dev-only noise and are dropped. Runtime pins: dbt-core 1.11.8 -> 1.12.0 typer 0.25.0 -> 0.27.0 SHA-pinned actions (ci, e2e, nightly-e2e, publish): actions/checkout v6.0.3 -> v7.0.1 astral-sh/setup-uv v7.6.0 -> v9.0.0 Verified: uv lock resolves, 683 passed / 3 skipped. Note: dbt-core 1.12.0 reshapes the tree more than the version implies - adds metricflow 0.211.0, drops dbt-semantic-interfaces, and pulls dbt-core-experimental-parser 2.0.0a5 (a prerelease, admitted by the existing prerelease = 'if-necessary-or-explicit' policy). Lockfile grows 109 -> 113 packages. These flow into dogfood, which pins to match. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
JesuFemi-O
force-pushed
the
chore/deps-review-v0.1.11
branch
from
August 2, 2026 13:23
cbd7d42 to
fed2f98
Compare
Contributor
|
@db-tycoon-stephen conflicts are resolved — rebased onto |
4 tasks
db-tycoon-stephen
added a commit
that referenced
this pull request
Aug 5, 2026
- pyproject + __init__ to 0.1.11, lockfile refreshed - CHANGELOG [0.1.11] entry: M2 schema work (#83/PR #190), ruff pin + format gate (PR #174), release-time dependency review (PR #180), and the four T2-4 review follow-ups closed on this branch (#185-#188) - docs/releases/v0.1.11.md + mkdocs nav entry Release date matches the planned 2026-08-07; adjust before tagging if the train slips. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Important
Do not merge until #174 lands. Two reasons:
ci.yml, and chore(lint): pin ruff 0.15.20, fix pre-existing violations from 0.16.0 upgrade #174 rewrites theInstall uv/Ruff lintregion this PR touches. Whichever merges second needs a manual resolve — so land chore(lint): pin ruff 0.15.20, fix pre-existing violations from 0.16.0 upgrade #174 first and rebase this on top.v0.1.11still runs unpinneduvx ruff check, so a green or red result on this PR depends on when it ran, not on what changed. chore(lint): pin ruff 0.15.20, fix pre-existing violations from 0.16.0 upgrade #174's ruff pin is what makes the signal reproducible. Verification below was done locally against a fixed toolchain instead.Summary
Replaces the eight Dependabot PRs (#161–#168), all now closed. They targeted
main, whichCONTRIBUTING.mdexcludes, and their green checks predated a ruff release so they weren't reproducible. Per #179, routine version updates move to a deliberate review at release-branch cut — this is the first one.Carries forward only the four bumps with real reach.
pytest,mkdocs-materialandsyrupywere dev-only and are dropped.dbt-coretyperactions/checkoutastral-sh/setup-uvAction SHAs were taken from the closed Dependabot PRs rather than looked up, and applied across all four workflow files (
ci,e2e,nightly-e2e,publish).Reviewer note:
dbt-core1.12.0 is bigger than the version suggestsThis is the one worth a real look. The bump reshapes the dependency tree:
metricflow0.211.0, dropsdbt-semantic-interfacesdbt-core-experimental-parser2.0.0a5 — a prerelease, admitted by the existingprerelease = "if-necessary-or-explicit"setting in[tool.uv]These pins propagate downstream to consumers that match
database-tycoon's versions, so an alpha parser entering the tree via a routine minor bump is a deliberate decision, not a detail. If that's unwanted, splitdbt-coreout and shiptyper+ the two actions alone — the rest of this PR stands on its own.This is exactly the class of change that would have slipped through had #165 been merged on its stale green check.
Verification
Run locally against
v0.1.11+ these changes:uv lock— resolves cleanly, no conflict betweendbt-core==1.12.0anddbt-duckdb==1.10.1uv run pytest -q— 683 passed, 3 skipped, 1 deselected🤖 Generated with Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.