update 2025-05-05

[NobbZ]

Summary by CodeRabbit

• Chores
  • Updated multiple plugins to newer versions and revisions, ensuring the latest features and fixes are available. No changes to application logic or user interface.

[coderabbitai]

Walkthrough

The change updates the npins/sources.json file by advancing the pinned versions, revisions, URLs, and hashes for multiple Neovim plugins and modules. Only the references to external Git repositories are modified, with no changes to code logic, control flow, or exported entities.

Changes

File(s)	Change Summary
npins/sources.json	Updated pinned versions, revisions, URLs, and hashes for various Neovim plugins and modules.

Possibly related PRs

• update 2024 12 10 #11: Updates npins/sources.json by advancing pinned Git repository revisions, URLs, and hashes for multiple Neovim plugins.
• update 2025-04-06 #50: Advances pinned Git repository versions, revisions, URLs, and hashes in npins/sources.json without code logic changes.
• update 2024 12 25 #12: Updates pinned Git repository versions for various Neovim plugins and components in npins/sources.json, reflecting newer commits and releases.

Poem

Hopping through plugins, hashes anew,
Each commit a carrot, fresh and true.
Revisions leap, rainbows gleam,
Catppuccin dreams in a Neovim stream.
With every pin, the garden grows—
A rabbit’s update, as springtime shows! 🥕🌱

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 37c71f1 and 5400900.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

• npins/sources.json (15 hunks)

🔇 Additional comments (14)

npins/sources.json (14)

53-56: Approved: Pinned update for nvim-augment.
The GitRelease entry has been correctly bumped to version v0.28.0, and the accompanying revision, url, and hash follow the established pattern.

---

67-69: Approved: Pinned update for nvim-catppuccin.
The updated revision, url, and hash align with the new commit on main.

---

80-82: Approved: Pinned update for nvim-crates.
The revision, url, and hash have been advanced correctly.

---

106-108: Approved: Pinned update for nvim-gitsigns.
The new revision, url, and hash reflect the latest upstream commit.

---

132-134: Approved: Pinned update for nvim-leap.
The revision, url, and hash have been updated to the specified snapshot.

---

145-147: Approved: Pinned update for nvim-lspconfig.
The metadata fields (revision, url, hash) correctly point to the new commit.

---

171-173: Approved: Pinned update for nvim-lspsaga.
All three fields have been bumped in line with the latest release.

---

184-186: Approved: Pinned update for nvim-luasnip.
The revision, url, and hash entries match the new upstream commit.

---

197-199: Approved: Pinned update for nvim-lz-n.
Revision, archive URL, and checksum have been correctly incremented.

---

223-225: Approved: Pinned update for nvim-mini.
The new commit hash and associated metadata are in order.

---

236-238: Approved: Pinned update for nvim-nabla.
Fields revision, url, and hash reflect the latest upstream state.

---

278-280: Approved: Pinned update for nvim-none-ls.
The pinned revision, download URL, and checksum have been updated correctly.

---

378-380: Approved: Pinned update for nvim-rainbow.
The new GitLab commit, archive endpoint, and hash are consistent.

---

404-406: Approved: Pinned update for nvim-surround.
Revision, URL, and hash correctly reference the latest main commit.

---

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.

Support

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

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 generate sequence diagram to generate a sequence diagram of the changes in 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.

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.