ele 4942 update lock file

[NoyaArie]

null

Summary by CodeRabbit

• Chores
  • Streamlined dependency lockfile metadata by removing redundant name labels, keeping package, version, and source checksums intact.
  • Improves consistency across dependencies and reduces noise in version control.
  • No functional, UI, or behavioral changes; installs, builds, and runtime behavior remain unchanged.
  • No action required for users or operators.
  • Compatibility unaffected across environments.

[linear]

ELE-4942 Dimension and column anomalies visualization

[coderabbitai]

Walkthrough

Removes two name fields from elementary/monitor/dbt_project/package-lock.yml, retaining package, version, git, revision, and sha1_hash values. No new files added, no logic changes, and no public APIs altered.

Changes

Cohort / File(s)	Summary
Package lock metadata cleanup elementary/monitor/dbt_project/package-lock.yml	Removed explicit name fields for dbt_utils and elementary entries; preserved package/version/git/revision/sha1_hash values.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• using elementary 0.19.0 #1942 — Also updates dbt package metadata in the same package-lock.yml, touching the elementary dependency entries.

Suggested reviewers

• ofek1weiss

Poem

A hop through YAML fields I go,
Pluck “name” tags, light as snow.
Packages stay, their hashes true—
Just tidying burrows, nothing new.
Thump-thump! My paws leave cleaner trails,
Configs aligned, no extra tails. 🐇✨

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch ele-4942-package-update

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

👋 @NoyaArie
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]

Actionable comments posted: 0

🧹 Nitpick comments (1)

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

2-5: Avoid hand-editing machine-generated lockfiles.

package-lock.yml is usually generated by dbt deps and may be overwritten. If this change is intentional, add a short note in the PR description confirming it reflects the output of running dbt deps with the project’s current dbt-core version.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• 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 d0bc714 and 29523af.

📒 Files selected for processing (1)

• elementary/monitor/dbt_project/package-lock.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). (1)

• GitHub Check: code-quality

🔇 Additional comments (2)

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

6-6: sha1_hash appears at top-level; verify intended indentation.

In dbt lockfiles, sha1_hash is typically nested under the corresponding package mapping. Here it’s at the root level, which may be ignored or rewritten. Confirm and, if needed, indent it under the relevant package.

If the hash belongs to the git dependency on Line 4, this is the likely fix:

-sha1_hash: 01feb82f69ff6c22843c3ccc6dce57c355417a9e
+    sha1_hash: 01feb82f69ff6c22843c3ccc6dce57c355417a9e

---

2-5: Confirm dbt-core version and lockfile schema compatibility

Please verify that your project is using a dbt-core version whose lockfile schema no longer requires the name: key (dbt v1.0+ uses schema v2). Without this confirmation, removing name: may cause dbt deps to rewrite or error.

• Paths to check

• elementary/monitor/dbt_project/package-lock.yml (lines 2–5)

• Actions

1. Confirm your dbt-core version (e.g. run dbt --version or inspect your dependency files such as requirements.txt, Pipfile, pyproject.toml, Dockerfiles, or CI workflows).
2. On a clean checkout, run dbt deps and ensure the generated package-lock.yml matches the one checked in (i.e. it still omits name:).

If you discover you’re on dbt <1.0 (lockfile schema v1), please restore the name: entries or upgrade dbt to avoid runtime errors.