Skip to content

docs: remove old nvim version requirements#1764

Open
ALameLlama wants to merge 1 commit into
AstroNvim:mainfrom
ALameLlama:docs/remove-old-nvim-version-requirements
Open

docs: remove old nvim version requirements#1764
ALameLlama wants to merge 1 commit into
AstroNvim:mainfrom
ALameLlama:docs/remove-old-nvim-version-requirements

Conversation

@ALameLlama
Copy link
Copy Markdown
Member

📑 Description

I noticed that a few plugins still have nvim version that we either don't support or are now the minimum required for AstroNvim v6 so I think it's save to remove them

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 9, 2026

Review Checklist

Does this PR follow the [Contribution Guidelines](development guidelines)? Following is a partial checklist:

Proper conventional commit scoping:

  • If you are adding a new plugin, the scope would be the name of the category it is being added into. ex. feat(utility): added noice.nvim plugin

  • If you are modifying a pre-existing plugin or pack, the scope would be the name of the plugin folder. ex. fix(noice-nvim): fix LSP handler error

  • Pull request title has the appropriate conventional commit type and scope where the scope is the name of the pre-existing directory in the project as described above

  • README is properly formatted and uses fenced in links with <url> unless they are inside a [title](url)

  • Entry returns a single plugin spec with the new plugin as the only top level spec (not applicable for recipes or packs).

  • Proper usage of opts table rather than setting things up with the config function.

  • Proper usage of specs table for all specs that are not dependencies of a given plugin (not applicable for recipes or packs).

Copy link
Copy Markdown
Member

@Uzaaft Uzaaft left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

-14 diff me likey :shipit:

@Uzaaft
Copy link
Copy Markdown
Member

Uzaaft commented May 16, 2026

@mehalter need a senpai merge on this.

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