Skip to content

Conversation

@NobbZ
Copy link
Owner

@NobbZ NobbZ commented Feb 28, 2025

Summary by CodeRabbit

  • Chores
    • Upgraded multiple core dependencies and updated integrity checks to enhance stability and security.
    • Removed deprecated dependency references and refreshed plugin versions to ensure smoother, more reliable performance.
    • Updated build configurations to align with the latest integrated components, contributing to overall system reliability.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 28, 2025

📝 Walkthrough

Walkthrough

The pull request updates dependency metadata across multiple files. In deps.txt, several dependency URLs and SHA256 checksums are updated with new versions for LUV, TREESITTER_QUERY, and TREESITTER. Two dependencies, CAT and TEE, are removed. In npins/sources.json, revision, URL, and hash fields for various plugin repositories are updated to reference new commit versions. In nvim.nix, the cargoHash for the tree-sitter override is updated to a new value.

Changes

File(s) Change Summary
deps.txt Updated URLs and SHA256 checksums: LUV from v1.48.0-2 to v1.50.0-1; TREESITTER_QUERY from v0.4.0 to v0.5.0; TREESITTER from v0.25.1 to v0.25.2; removed CAT and TEE dependencies.
npins/sources.json Revised the revision, url, and hash fields for multiple plugins (e.g., neovim, nvim-crates, nvim-gitsigns, etc.) to point to updated commits and archives.
nvim.nix Updated the cargoHash for the tree-sitter override from sha256-paxcZGps0g9+... to sha256-TthRC6d1tEuao8vSptqxXtR0XRPIkU....

Possibly related PRs

  • update 2025 01 20 #13: Modifies dependency URLs and SHA256 checksums in deps.txt, including changes to the TREESITTER dependency.
  • update 2024 12 10 #11: Addresses dependency updates in the nvim-lspconfig entry, aligning with the changes in this PR.
  • update 2025 02 03 #23: Updates dependency references in both deps.txt and npins/sources.json, showing a strong connection to the modifications here.

Poem

I'm a rabbit hopping in code delight,
Watching dependencies change day and night.
URLs and checksums all spiffed and new,
With each update, my joy only grew!
Carrots and commits, in a neat array 🥕
My little heart cheers every PR day!


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 33222da and cf31f16.

📒 Files selected for processing (3)
  • deps.txt (2 hunks)
  • npins/sources.json (15 hunks)
  • nvim.nix (1 hunks)
🧰 Additional context used
🪛 LanguageTool
deps.txt

[style] ~13-~13: The word ‘LUV’ is informal and non-standard.
Context: ...b.com/luvit/luv/archive/1.50.0-1.tar.gz LUV_SHA256 bb4f0570571e40c1d2a7644f6f9c1309...

(LUV)

🔇 Additional comments (6)
nvim.nix (1)

62-62: Updated cargoHash for tree-sitter

The cargoHash value has been updated to match the new tree-sitter version (0.25.2) referenced in deps.txt. This ensures integrity checking works correctly with the updated dependency.

deps.txt (3)

13-14: Updated LUV dependency to version 1.50.0-1

The dependency update from version 1.48.0-2 to 1.50.0-1 with corresponding SHA256 hash update is a routine maintenance change.

🧰 Tools
🪛 LanguageTool

[style] ~13-~13: The word ‘LUV’ is informal and non-standard.
Context: ...b.com/luvit/luv/archive/1.50.0-1.tar.gz LUV_SHA256 bb4f0570571e40c1d2a7644f6f9c1309...

(LUV)


45-46: Updated TREESITTER_QUERY to version 0.5.0

The tree-sitter-query dependency has been upgraded from v0.4.0 to v0.5.0 with the appropriate SHA256 checksum update.


49-50: Updated TREESITTER to version 0.25.2

The core tree-sitter library has been upgraded from v0.25.1 to v0.25.2 with matching SHA256 checksum. This minor version update should provide bug fixes and improvements.

npins/sources.json (2)

35-37: Updated neovim repository reference

The neovim source has been updated to a new commit with corresponding URL and hash updates.


47-49: Updated multiple Neovim plugin references

Multiple Neovim plugins have been updated to their latest versions with corresponding revision, URL, and hash updates. This is standard maintenance to keep the plugin ecosystem current.

Also applies to: 71-73, 95-97, 107-109, 143-145, 179-181, 229-232, 242-244, 281-283, 305-307, 317-319, 365-367, 377-379


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 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.
    • Generate unit testing code for this file.
    • 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. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • 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 src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

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

Documentation and Community

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

@NobbZ NobbZ merged commit 352924b into main Feb 28, 2025
1 check passed
@coderabbitai coderabbitai bot mentioned this pull request Feb 28, 2025
@coderabbitai coderabbitai bot mentioned this pull request Mar 11, 2025
@coderabbitai coderabbitai bot mentioned this pull request Apr 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants