Ten plugins in lua/config/plugins.lua have no dedicated version-tracking issue (the remaining plugins are covered by #203, #169, #163). Checked each against upstream as of 2026-06-20.
Where: pins live in nvim-pack-lock.json, plugin specs in lua/config/plugins.lua:4-39.
| Plugin |
Pinned |
Latest upstream |
Status |
| blink.cmp |
50c696b (2026-06-19) |
2c36633 (2026-06-20), tag v1.10.2 |
1 commit behind (nerd-font fix, not config-relevant). v1.10.0 was flagged upstream as "final 1.x before 2.0" — a future 2.0 may restructure sources/keymap, worth re-checking when it lands. |
| blink.lib |
5876dd9 |
same |
up to date |
| fzf-lua |
267f5db |
same |
up to date (rolling-release repo, no tags) |
| conform.nvim |
619363c (2026-05-24) |
same, tag v9.1.0 |
up to date; pin postdates the v9.0.0 breaking cleanup, so current default_format_opts/formatters_by_ft usage is unaffected |
| nvim-lint |
01c9842 |
same |
up to date |
| gitsigns.nvim |
2038c66 |
same, tag v2.1.0 |
up to date; pin postdates the v2.0.0 major bump |
| nui.nvim |
de74099 |
same |
up to date (low-churn repo) |
| quicker.nvim |
4a6883c |
same, tag v1.5.1 |
up to date |
| vim-sneak |
feea86a |
same |
up to date (largely dormant upstream) |
| fff.nvim |
7d7910b, version-pinned to vim.version.range("0.9.4") |
v0.9.5 (2026-06-18) |
behind — see below |
fff.nvim is intentionally capped, now one release behind
lua/config/plugins.lua:10 pins version = vim.version.range("0.9.4"), which (per vim.pack semantics, single-arg range) means >=0.9.4,<0.9.5 — this deliberately blocks vim.pack.update() from moving to v0.9.5, per the inline comment "this package breaks frequently, specify version" (history backs this up: #173 bumped 0.9.0→0.9.4 for the same reason).
v0.9.5 adds: resume-last-picker, Python bindings, fuzzy-match/perf improvements. No confirmed breaking changes found, but this is exactly the plugin the config's own comment warns about, and the rust binary gets rebuilt via the PackChanged autocmd in plugin_config.lua:211-221 on update — that rebuild can't be verified in this sandboxed environment (no cargo/binary toolchain here).
Recommended action: bump the range to vim.version.range("0.9.5") in lua/config/plugins.lua:10 and the corresponding nvim-pack-lock.json rev, then run :SyncPkgs and confirm find_files/live_grep and the binary rebuild still work before committing — same workflow as #173. Given the plugin's own fragility warning, recommend doing this as a manual, tested follow-up rather than an unverified automated PR.
Bottom line: all ten plugins are well-maintained and current except fff.nvim, which is one minor version behind by design.
Ten plugins in
lua/config/plugins.luahave no dedicated version-tracking issue (the remaining plugins are covered by #203, #169, #163). Checked each against upstream as of 2026-06-20.Where: pins live in
nvim-pack-lock.json, plugin specs inlua/config/plugins.lua:4-39.50c696b(2026-06-19)2c36633(2026-06-20), tag v1.10.2sources/keymap, worth re-checking when it lands.5876dd9267f5db619363c(2026-05-24)default_format_opts/formatters_by_ftusage is unaffected01c98422038c66de740994a6883cfeea86a7d7910b, version-pinned tovim.version.range("0.9.4")fff.nvim is intentionally capped, now one release behind
lua/config/plugins.lua:10pinsversion = vim.version.range("0.9.4"), which (pervim.packsemantics, single-arg range) means>=0.9.4,<0.9.5— this deliberately blocksvim.pack.update()from moving to v0.9.5, per the inline comment "this package breaks frequently, specify version" (history backs this up: #173 bumped 0.9.0→0.9.4 for the same reason).v0.9.5 adds: resume-last-picker, Python bindings, fuzzy-match/perf improvements. No confirmed breaking changes found, but this is exactly the plugin the config's own comment warns about, and the rust binary gets rebuilt via the
PackChangedautocmd inplugin_config.lua:211-221on update — that rebuild can't be verified in this sandboxed environment (no cargo/binary toolchain here).Recommended action: bump the range to
vim.version.range("0.9.5")inlua/config/plugins.lua:10and the correspondingnvim-pack-lock.jsonrev, then run:SyncPkgsand confirmfind_files/live_grepand the binary rebuild still work before committing — same workflow as #173. Given the plugin's own fragility warning, recommend doing this as a manual, tested follow-up rather than an unverified automated PR.Bottom line: all ten plugins are well-maintained and current except fff.nvim, which is one minor version behind by design.