Updated DBT pacakge revision

[elazarlachkar]

null

Summary by CodeRabbit

• Chores
  • Updated an internal package dependency to a newer revision as part of routine maintenance.
  • No user-facing functionality, behavior, or configuration was changed.
  • Intended to keep dependencies current for ongoing compatibility and stability.
  • No action required from users; workflows should continue to operate as before.

[linear]

ELE-5095 Dremio: Duplication in synced schema

[coderabbitai]

Walkthrough

Updates the dbt-data-reliability git dependency revision and corresponding lock metadata in two files within elementary/monitor/dbt_project. No functional or control-flow changes.

Changes

Cohort / File(s)	Summary
DBT dependency revision update elementary/monitor/dbt_project/packages.yml, elementary/monitor/dbt_project/package-lock.yml	Bump git revision of elementary-data/dbt-data-reliability from 0f59f9f... to 2265cff...; update lock sha1 from 0dde8f6... to 643cf31.... No other edits.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• update dbt package revision #2003 — Prior switch to git-based dbt-data-reliability dependency; this PR advances the referenced commit.
• Update DBT package version #2012 — Previous update to commit 0f59f9f...; current PR moves to 2265cff....
• changed dbt package version to a commit with dremio types mapping. ne… #1985 — Earlier commit pin change for the same dbt-data-reliability repo.

Suggested reviewers

• ofek1weiss
• michael-myaskovsky

Poem

Hop hop! I tweak a tiny thread,
A commit hash nudged ahead.
No models moved, no macros spun—
Just pins aligned, and then I’m done.
In the burrow logs I gleam,
“Locked and loaded,” squeaks my beam. 🥕✨

Pre-merge checks and finishing touches

✅ 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 succinctly identifies the primary change—updating a DBT package revision in the project configuration—and avoids generic or unrelated wording, giving clear context for reviewers scanning the history. Although there is a minor typo in “pacakge,” the phrasing remains specific to the metadata update rather than vague or misleading.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch ele-5095-dremio-duplication-in-synced-schema

---

📜 Recent review details

Configuration used: CodeRabbit UI

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 d7f7d9b and 620c703.

📒 Files selected for processing (2)

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

⏰ 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 (1)

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

5-6: Lock metadata matches the new revision
Thanks for refreshing both the revision and sha1_hash to 2265cff62f4514390d97db02dd862c197353aed2 / 643cf3145ac135c679505d2319a262eac54237bd so they stay in sync with packages.yml. Nothing else needed here.

---

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

[github-actions]

👋 @elazarlachkar
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.