Update package import

[will-warner]

Updating elementary dbt package import to ref dbt's package hub rather than git.

Elementary currently fails to run in environments that dont have Git installed, I believe because of this.

Summary by CodeRabbit

• Chores
  • Updated Elementary package to version 0.22.1
  • Improved dependency management configuration by transitioning to standard package specifications for enhanced stability

[github-actions]

👋 @will-warner
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

The dbt project's package dependencies were updated to use standard named package specifications instead of git-based references, replacing the git-based elementary-data/dbt-data-reliability dependency with elementary-data/elementary version 0.22.1, with corresponding lock file updates.

Changes

Cohort / File(s)	Summary
dbt Package Dependency Configuration elementary/monitor/dbt_project/packages.yml, elementary/monitor/dbt_project/package-lock.yml	Transitioned from git-based dependency references to named package specifications. Replaced git-based elementary-data/dbt-data-reliability with named elementary-data/elementary version 0.22.1. Updated package hashes and lock file entries to reflect the new package structure.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 Dependencies dance in measured time,
Git to packages—a structured climb,
Elementary 0.22.1 takes the stage,
Locked and ready, a new page! ✨

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Update package import' directly relates to the main change: replacing git-based package dependencies with named package entries from dbt's package hub, addressing the core issue of Git availability.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into master

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

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

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

12-13: ⚠️ Potential issue | 🟡 Minor

Stale version in the commented-out template.

The commented fallback on Line 13 still references 0.22.0 while the active dependency is 0.22.1. Consider bumping it to keep the template in sync.

Proposed fix

   # - package: elementary-data/elementary
-  #   version: 0.22.0
+  #   version: 0.22.1

🤖 Fix all issues with AI agents

In `@elementary/monitor/dbt_project/packages.yml`:
- Around line 4-5: The packages.yml lists package: elementary-data/elementary
with version 0.22.1 which doesn't exist on the dbt hub; update that version to
the published one (0.20.1) or confirm and change it to the intended published
tag before running dbt deps; specifically edit the packages.yml entry for
package: elementary-data/elementary and set version: 0.20.1 (or the correct
published version) so dbt deps will succeed.