update 2025-04-13

[NobbZ]

Summary by CodeRabbit

• Chores
  • Upgraded multiple underlying components to their latest versions, enhancing overall stability and performance.
  • Implemented dependency updates that improve integration and smooth operation of features like notifications, navigation, and language-server support.
  • Minor version bumps provide a more reliable and robust experience.

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request updates the plugin information in the npins/sources.json file. Revisions, URLs, and hash values have been updated for several Git repository entries. Specifically, entries for plugins like nvim-crates, nvim-gitsigns, nvim-leap, nvim-lspconfig, nvim-lz-n, nvim-rainbow, and nvim-notify have been modified. Additionally, the nvim-ufo entry has been upgraded from version v1.4.0 to v1.5.0 alongside its other fields. There are no changes to public or exported entities.

Changes

File(s)	Change Summary
npins/sources.json (nvim-crates, nvim-gitsigns, nvim-leap, nvim-lspconfig, nvim-lz-n, nvim-rainbow, nvim-notify)	Updated revision, url, and hash fields to reference new commit versions.
npins/sources.json (nvim-ufo)	Upgraded version from v1.4.0 to v1.5.0 and updated revision, url, and hash values.

Sequence Diagram(s)

(No sequence diagram generated as the changes do not introduce new control flows or features.)

Poem

I'm a little rabbit with a big hop of glee,
For updated commits and fresh code, you see.
Revisions and URLs now prance in line,
Hashes renewed like a well-tuned design.
With every update, my burrow sings—a joyful, leaping spree! 🐇

---

📜 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 2c2fbfe and cb27bf5.

⛔ Files ignored due to path filters (1)

• flake.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• npins/sources.json (10 hunks)

🔇 Additional comments (10)

npins/sources.json (10)

80-82: [nvim-crates] Validate Plugin Update Details
The revision, URL, and hash for the nvim-crates plugin have been updated. Please verify that these new values match the official commit in the plugin’s repository to ensure integrity of the download artifacts.

---

106-108: [nvim-gitsigns] Confirm Updated Repository Fields
The nvim-gitsigns entry now reflects a new revision, URL, and hash. Please double-check that these details are in line with the intended version update from the upstream repository.

---

132-134: [nvim-leap] Verify Plugin Revision and Assets
The updated fields (revision, URL, and hash) for nvim-leap have been provided. Ensure that these changes accurately reflect the latest stable commit and that the tarball URL is correct.

---

145-147: [nvim-lspconfig] Check Updated Plugin Data
For nvim-lspconfig, the revision, URL, and hash have been updated. Please verify that these values correspond to the desired release and that no unexpected breaking changes have been introduced with the update.

---

197-199: [nvim-lz-n] Confirm Updated Plugin Information
The nvim-lz-n plugin’s revision, URL, and hash have been updated. It is advisable to cross-check these fields with the official repository to ensure the correct artifact is fetched during builds.

---

223-225: [nvim-mini] Validate Revised Plugin Details
The update for nvim-mini now includes new revision, URL, and hash values. Please confirm that these fields are accurate and align with the latest release from the repository.

---

278-280: [nvim-none-ls] Verify Plugin Update Credentials
The nvim-none-ls plugin has updated its revision, URL, and hash. Ensure that these changes reflect the current version as intended in your configuration and match the repository’s state.

---

291-293: [nvim-notify] Confirm Updated Plugin Metadata
The new values for revision, URL, and hash under nvim-notify have been provided. Please verify that these fields are accurate according to the latest release available from the official GitHub repository.

---

322-325: [nvim-nvim-ufo] Assess Version Upgrade Impact
The nvim-nvim-ufo plugin has been upgraded from v1.4.0 to v1.5.0 with corresponding updates to its revision, URL, and hash. It is essential to review if any API or behavioral changes in v1.5.0 could affect your configuration.

---

378-380: [nvim-rainbow] Validate Repository Field Changes
The revision, URL, and hash for nvim-rainbow have been updated. Please ensure these values are correct and that the new URL correctly points to the updated archive from GitLab.

---

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 plan to trigger planning for file edits and PR creation.
• @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.