Skip to content

[deps] fff.nvim: bump version pin from 0.9.0 to 0.9.4 #173

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
stanfish06 merged 1 commit into from
Jun 10, 2026
Merged

[deps] fff.nvim: bump version pin from 0.9.0 to 0.9.4 #173

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion lua/config/plugins.lua
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ local package_list = {
name = "fff.nvim",
src = "https://github.com/dmtrKovalenko/fff.nvim",
lazy = true,
version = vim.version.range("0.9.0"),
version = vim.version.range("0.9.4"),

@chatgpt-codex-connector chatgpt-codex-connector Bot Jun 10, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Pin fff.nvim to an existing release tag

This pins vim.pack to an exact 0.9.4 range, but upstream currently has v0.9.3 and nightly 0.9.4-nightly.* tags, not a stable 0.9.4/v0.9.4 tag; Neovim's vim.version.range() docs also note that suffixed versions like prereleases are not matched by plain range specs. In a clean/update :SyncPkgs run, vim.pack.update() has no matching semver tag to resolve, so the dependency bump cannot actually apply; use an existing stable tag/range or pin the intended nightly tag as a string.

Useful? React with 👍 / 👎.

@chatgpt-codex-connector chatgpt-codex-connector Bot Jun 10, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Update the pack lock entry with the version bump

Because nvim-pack-lock.json is tracked and still records fff.nvim at the old revision/version, fresh checkouts use the lockfile revision instead of resolving this new spec on the first vim.pack.add() call. That means someone syncing this config can still get fff.nvim 0.9.0 despite this line saying 0.9.4, until they manually run and confirm a pack update; commit the matching lockfile update with the spec bump so the dependency change is reproducible.

Useful? React with 👍 / 👎.

}, -- this package breaks frequently, specify version
{ name = "nvim-lspconfig", src = "https://github.com/neovim/nvim-lspconfig" },
{ name = "sneaks.vim", src = "https://github.com/justinmk/vim-sneak" }, -- remaps s/S intentionally
Expand Down
Loading