update dbt package reference

[haritamar]

null

Summary by CodeRabbit

• Chores
  • Updated dbt package dependencies to use an alternate source for the data reliability package.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[linear]

ELE-5191 Fix for the logic updating test_result_rows

[github-actions]

👋 @haritamar
Thank you for raising your pull request.
Please make sure to add tests and document all user-facing changes.
You can do this by editing the docs files in this pull request.

[coderabbitai]

📝 Walkthrough

Walkthrough

This change swaps the elementary dbt package source from the published version 0.21.0 to a git-based dependency pointing to a specific commit in the dbt-data-reliability repository, with corresponding lock file updates.

Changes

Cohort / File(s)	Summary
dbt Package Configuration elementary/monitor/dbt_project/packages.yml, elementary/monitor/dbt_project/package-lock.yml	Replaced published elementary-data/elementary v0.21.0 with git-based dependency (dbt-data-reliability.git at revision 96f29dce3711f38c63f992bcaf8848b101d63194) and updated corresponding lock file sha1 hash.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

• using elementary 0.19.0 #1942: Modifies the same dbt package entries in packages.yml and package-lock.yml but transitions the elementary dependency to a different source/version.

Suggested reviewers

• ofek1weiss

Poem

🐰✨ A git commit hops into place,
Where the published package used to race,
Locks and configs now align so tight,
dbt-data-reliability shines bright! 🌟

Pre-merge checks

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'update dbt package reference' directly describes the main change: replacing a dbt package dependency from a published version to a git-based reference.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

elementary/monitor/dbt_project/packages.yml (1)

4-5: Consider adding a comment explaining the specific commit.

The git-based dependency change aligns with the pattern for unreleased versions noted in the comments below. However, consider adding a brief inline comment explaining why this specific commit is needed (e.g., referencing the ELE-5191 fix mentioned in the PR title) to help future maintainers understand the temporary nature of this dependency.

🔎 Suggested enhancement with explanatory comment

+ # Using commit with fix for ELE-5191 (test_result_rows logic update)
  - git: https://github.com/elementary-data/dbt-data-reliability.git
    revision: 96f29dce3711f38c63f992bcaf8848b101d63194

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 3624b8b and b5c4bc2.

📒 Files selected for processing (2)

• elementary/monitor/dbt_project/package-lock.yml
• elementary/monitor/dbt_project/packages.yml

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: test / test
• GitHub Check: code-quality

🔇 Additional comments (2)

elementary/monitor/dbt_project/package-lock.yml (1)

4-6: Lock file correctly reflects the git-based dependency.

The lock file change appropriately switches from a published package to a git-based dependency. The specified commit revision is valid and accessible in the repository, with the commit message "update dbt package reference" aligning with the intended change.

elementary/monitor/dbt_project/packages.yml (1)

4-5: Git commit is valid and accessible.

The commit 96f29dce3711f38c63f992bcaf8848b101d63194 exists and contains the expected test_result_rows changes:

• Commit message: "test_result_rows: add row_index and test_type"
• Modified files include models/edr/run_results/test_result_rows.sql and related test handling logic