chore: bump @altimateai/dbt-integration to 0.3.0#1936
Conversation
Drop the trailing `DbtCloudVariantDetector` argument from the `DBTFusionCommandProjectIntegration` factory; 0.3.0 removed it from that constructor (the cloud integration still takes it). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
WalkthroughDependency ChangesDependency Update & Wiring Alignment
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@package.json`:
- Line 1345: The Fusion-path change removed DbtCloudVariantDetector from the
DBTFusionCommandProjectIntegration factory but the dbt Fusion smoke test is
still pending and there may be other Fusion bindings still injecting
DbtCloudVariantDetector; run the suggested smoke test, update or add tests to
exercise the DBTFusionCommandProjectIntegration paths, and search the codebase
for any remaining references to DbtCloudVariantDetector (ensure only
DBTCloudProjectIntegration references it) and remove or refactor those
injections so the Fusion factories no longer accept or pass
DbtCloudVariantDetector; verify DBTFusionCommandProjectIntegration and
DBTCloudProjectIntegration behavior after changes.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 641d3b65-b359-4c3d-94d3-8c09d7d03988
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (2)
package.jsonsrc/inversify.config.ts
💤 Files with no reviewable changes (1)
- src/inversify.config.ts
| ], | ||
| "dependencies": { | ||
| "@altimateai/dbt-integration": "^0.2.14", | ||
| "@altimateai/dbt-integration": "^0.3.0", |
There was a problem hiding this comment.
Confirm dbt Fusion smoke test and verify no remaining DbtCloudVariantDetector injections on the Fusion path.
The PR notes the dbt Fusion smoke test as pending. Given that the sole behavioral change here is the removal of DbtCloudVariantDetector from the DBTFusionCommandProjectIntegration factory, please ensure the smoke test is completed before merging. Additionally, verify there are no other Fusion-path factory/binding sites that still pass DbtCloudVariantDetector.
#!/bin/bash
# Description: Find all constructor/factory usages of DBTFusionCommandProjectIntegration
# and any remaining DbtCloudVariantDetector bindings associated with the Fusion path.
# Expected: Only the DBTCloudProjectIntegration factory should reference DbtCloudVariantDetector.
rg -n "DBTFusionCommandProjectIntegration" --type ts -A 5 -B 2
echo "---"
rg -n "DbtCloudVariantDetector" --type ts -C 3🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@package.json` at line 1345, The Fusion-path change removed
DbtCloudVariantDetector from the DBTFusionCommandProjectIntegration factory but
the dbt Fusion smoke test is still pending and there may be other Fusion
bindings still injecting DbtCloudVariantDetector; run the suggested smoke test,
update or add tests to exercise the DBTFusionCommandProjectIntegration paths,
and search the codebase for any remaining references to DbtCloudVariantDetector
(ensure only DBTCloudProjectIntegration references it) and remove or refactor
those injections so the Fusion factories no longer accept or pass
DbtCloudVariantDetector; verify DBTFusionCommandProjectIntegration and
DBTCloudProjectIntegration behavior after changes.
Bundle Size Reportdarwin-arm64: 74.2 MB
linux-x64: 75.9 MB
win32-x64: 76.8 MB
|
Summary
@altimateai/dbt-integrationfrom^0.2.14to^0.3.0(package.json+package-lock.json).DbtCloudVariantDetectorargument from theDBTFusionCommandProjectIntegrationfactory insrc/inversify.config.ts— 0.3.0 removed it from that constructor (theDBTCloudProjectIntegrationfactory still passes it, matching the unchanged cloud signature).Test plan
npx tsc --noEmit(clean)npm run test-compile(clean)npm test— 30 suites / 477 tests pass🤖 Generated with Claude Code
Summary by CodeRabbit