[deps] fff.nvim: bump version pin from 0.9.0 to 0.9.4#173
Conversation
v0.9.4 is the latest release (Jun 2026). The plugin is intentionally pinned because it breaks frequently; this manually advances the pin. Run :SyncPkgs to apply — the lock file will update automatically. Closes part of #152. https://claude.ai/code/session_01WfHniedWQBWikXmdJFVwur
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 08d837a9fa
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| src = "https://github.com/dmtrKovalenko/fff.nvim", | ||
| lazy = true, | ||
| version = vim.version.range("0.9.0"), | ||
| version = vim.version.range("0.9.4"), |
There was a problem hiding this comment.
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 👍 / 👎.
| src = "https://github.com/dmtrKovalenko/fff.nvim", | ||
| lazy = true, | ||
| version = vim.version.range("0.9.0"), | ||
| version = vim.version.range("0.9.4"), |
There was a problem hiding this comment.
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 👍 / 👎.
2 participants
What
Bumps the
fff.nvimversion pin inlua/config/plugins.luafrom"0.9.0"to"0.9.4".Where
lua/config/plugins.lua:10—version = vim.version.range("0.9.0")→vim.version.range("0.9.4")Why it matters
The plugin is intentionally pinned (comment: "this package breaks frequently, specify version"), so new releases require a manual bump. v0.9.4 is the latest release as of June 2026. Issue #152 originally tracked updating to v0.9.1; this PR advances directly to the current latest.
After merging
Run
:SyncPkgsto apply —vim.packwill resolve the new tag and updatenvim-pack-lock.jsonautomatically. ThePackChangedautocmd inplugin_config.luawill trigger a binary rebuild if needed.Test plan
:SyncPkgsand confirm fff.nvim installs at v0.9.4<leader>ff(find files) and<leader>fg(live grep) still workPackChangedautocmdAdvances #152.
Generated by Claude Code