fix(dbt-tools): run dbt Fusion without Python, and pin the stale-manifest fixes
Issue for this PR
Closes #1756.
Type of change
- Bug fix
What does this PR do?
dbt Fusion works through altimate-dbt with no Python. altimate-dbt's prerequisite check demanded Python and dbt-core in every mode. In Fusion mode it checks the project and a dbt 2.x binary (findDbtV2Binary, judged as the adapter does: script launchers count). The adapter gets "" when the config has no Python path. Other modes are unchanged.
Real dbt Fusion 2.0.9, {projectRoot, dbtIntegration: "fusion"}, PATH holding only dbt:
- main:
info,childrenanddoctorstop at "Prerequisites not met: python: No Python path configured". - this PR:
infoandchildren --model ordersanswer (no modelisExternalProject), anddoctorreports fusion ok and project ok. - no
dbtat all: "dbt Fusion was not found…".
Also:
- an end-to-end test pinning 0.3.19's stale-manifest fix;
- the stale shape in the six skill references;
- schema-verify's stale note drops an empty parse time.
Claims:
- C1: With
dbtIntegration: fusion, the checks arefusionandprojectonly, and a missing or emptypythonPathpasses. - C2: Other modes' checks and messages are as on main, and the Fusion lookup never runs.
- C3: The stale note quotes
written_atonly when it's a non-empty string.
How did you verify your code works?
- Fail on main: the Fusion prerequisite tests, the empty parse-time test; the stale test fails on dbt-integration 0.3.17.
- Local: typecheck 13/13; dbt-tools 124 pass; the stale test passes on dbt 1.8, 1.10 and 1.11; opencode validators 834 pass; leak and marker checks clean.
Cost side effects
None.
Checklist
- I have tested my changes locally
- I have not included unrelated changes in this PR
- I checked for cost side effects (model calls, queries or cloud resources that grow with user data) and described them, or wrote "none"
🤖 Generated with Claude Code
https://claude.ai/code/session_01VEmKQx8gR7vd6ettA3mWjP
Summary by cubic
Makes dbt Fusion work without Python, and pins the stale-manifest fixes.
In Fusion mode altimate-dbt now checks for a dbt 2.x binary instead of requiring Python and dbt-core, and a missing or empty pythonPath no longer fails the check. The lookup runs script launchers (asdf, nix, wrappers) and allows 15 s for --version, as the adapter does; dbt Core is still rejected. Other modes keep their existing checks.
Also pins @altimateai/dbt-integration 0.3.19's stale-manifest fix with an end-to-end test, updates the six altimate-dbt-commands.md skill references to describe the { stale_manifest, models } answer, and makes schema-verify's stale note omit an empty parse time.
Summary by CodeRabbit
- New Features
- Fusion mode now checks for a compatible dbt 2.x installation and provides guidance when one isn’t found. The check can run without a configured Python path.
- Bug Fixes
- Stale-manifest notices show a parse timestamp only when it’s valid and non-empty, and keep displayed values concise.
- Documentation
- Clarified that model relationships returned after a project check fails may reflect the last successful parse and be outdated. If no prior manifest is available, the commands return an error.