Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Time for a new stable release?

Open
#629 1 comment 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Stale
Tech stack
lua, neovim
Domain
release

Research direction

Start by reviewing plenary.nvim PR 575, which contains the referenced fix, and check the current stable version used by lazy.nvim. Done means publishing a new stable release that includes the fix; the issue names no files or tests.

Written by the indexing model from the issue text.

Description

As I'm running lazy.nvim with version = "*" I get the current stable version.
This includes the bug https://github.com/nvim-lua/plenary.nvim/pull/575, which causes problems with many other plugins.
I noticed it with codecompanion - see https://github.com/olimorris/codecompanion.nvim/discussions/361, but there seem to be many other plugins affected.

Any chance of getting a new stable release which includes this fix?

Dominant language
Lua
Stars
3.5k
Forks
340
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nvim-lua/plenary.nvim

All issues in nvim-lua/plenary.nvim

Similar issues

More Lua issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.