update 2025 03 11

[NobbZ]

• update nvim
• nvim-crates: update
• nvim-leap: update
• nvim-lspconfig: update
• nvim-lz-n: update
• nvim-none-ls: update
• nvim-precognition: update
• nvim-rainbow: update

Summary by CodeRabbit

• Chores
  • Updated several external dependency references and integrity checks to align with the latest upstream revisions.
  • Refreshed metadata for third-party plugins to ensure compatibility and maintain high reliability.

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request updates dependency references across several configuration files. In deps.txt, the URLs and SHA256 checksums for both LuaJIT and Tree-sitter have been updated. The metadata for the "nvim-rainbow" plugin in npins/sources.json now reflects a new revision, URL, and hash. Additionally, the cargoHash value within the tree-sitter override in nvim.nix has been modified to update the integrity verification of its Rust package.

Changes

File	Change Summary
deps.txt	Updated URLs and SHA256 checksums for LuaJIT and Tree-sitter dependencies.
npins/sources.json	Revised revision, URL, and hash for the nvim-rainbow plugin metadata.
nvim.nix	Modified the cargoHash in the tree-sitter override to update integrity verification data.

Possibly related PRs

• Update 2025 02 28 #25: Updates to the Tree-sitter dependency URL and checksum in deps.txt.
• fixes #10: Similar LuaJIT and Tree-sitter updates in deps.txt indicating direct code-level modifications.
• update 2024 12 25 #12: Changes align with updates to the LuaJIT and Tree-sitter URLs and checksums in deps.txt.

Poem

Hop, hop, I scurry with glee,
New dependency links set me free.
LuaJIT and Tree-sitter updated in sight,
nvim-rainbow shining ever so bright.
With a cargoHash tweak and a joyful byte,
I bound through code from morning to night!

---

📜 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 b4294fb and 7b323a9.

📒 Files selected for processing (10)

• deps.txt (2 hunks)
• npins/sources.json (1 hunks)
• nvim.nix (1 hunks)
• npins/sources.json (1 hunks)
• npins/sources.json (1 hunks)
• npins/sources.json (1 hunks)
• npins/sources.json (1 hunks)
• npins/sources.json (1 hunks)
• npins/sources.json (1 hunks)
• npins/sources.json (1 hunks)

🔇 Additional comments (4)

nvim.nix (1)

62-62: Hash update looks good for tree-sitter dependency

The updated cargoHash corresponds to the new version of tree-sitter (v0.25.3) that's also being updated in deps.txt. This change ensures the integrity verification for the Rust package works correctly with the new version.

npins/sources.json (1)

119-121: LGTM: nvim-lspconfig update

The revision, URL, and hash have been properly updated to reference the newer version of the nvim-lspconfig plugin. This aligns with the PR objectives to update various Neovim plugins.

deps.txt (2)

4-5: LuaJIT dependency update looks good

The URL and SHA256 checksum for LuaJIT have been updated to point to a newer version. The hash format is valid and this change is consistent with the PR's goal of updating Neovim dependencies.

---

49-50: Tree-sitter update from v0.25.2 to v0.25.3

The URL has been updated to reference tree-sitter v0.25.3 (from v0.25.2) and the corresponding SHA256 hash has been updated accordingly. This matches the cargoHash update in nvim.nix.

---

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

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