Update dbt package reference

[elazarlachkar]

null

Summary by CodeRabbit

• Chores
  • Updated data reliability monitoring dependencies to latest versions.

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

[linear]

CORE-261 Add identifier as comment to Cloud queries

[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.

[coderabbitai]

📝 Walkthrough

Walkthrough

Updated the git dependency revision for dbt-data-reliability from f5c062d to 9f64cbcaf across package manifest and lock file, maintaining consistency between dependency declarations.

Changes

Cohort / File(s)	Summary
Dependency Version Update elementary/monitor/dbt_project/package-lock.yml, elementary/monitor/dbt_project/packages.yml	Bumped git dependency revision for dbt-data-reliability repository and updated corresponding sha1_hash in lock file to keep package definitions synchronized

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5 minutes

Poem

🐰 A hop, skip, and git commit away,
Dependency versions dance and play!
From hash to hash, revision aligned,
Elementary updates, perfectly designed! ✨

🚥 Pre-merge checks | ✅ 3

✅ 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' accurately reflects the main change: updating the git dependency revision in both package-lock.yml and packages.yml for the dbt-data-reliability package.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@elementary/monitor/dbt_project/package-lock.yml`:
- Around line 5-6: The sha1_hash key in package-lock.yml is not indented under
the git package entry and will be treated as a top-level YAML key; fix it by
indenting sha1_hash to the same level as revision (e.g., the same number of
spaces before sha1_hash as before revision) so both keys are siblings under the
git entry, ensuring consistent YAML indentation for revision and sha1_hash.