[deps] Plugin version tracking — 16 pinned packages due for review #77

What

All 16 plugins are pinned to specific git commit SHAs in nvim-pack-lock.json. Several have had significant releases or structural changes since their pinned revisions. This is a tracking issue for the update cycle.

Where

nvim-pack-lock.json — all 16 entries.

Plugins with notable upstream changes

High priority

obsidian.nvim (896d4515) → current: v3.14.0

• Maintained fork moved to obsidian-nvim/obsidian.nvim (already using correct source)
• v3.14.0 has breaking changes: all opts.callback.* functions dropped the leading client parameter; opts.note_frontmatter_func → opts.frontmatter.func; opts.disable_frontmatter → opts.frontmatter.enabled
• Completion now only triggers on [[ (less intrusive)
• Legacy ObsidianQuickSwitch-style commands planned for removal
• Current config is minimal (workspaces + daily_notes) so immediate breakage is unlikely, but worth pinning to a tagged release and reading the Breaking Changes wiki before updating

nvim-treesitter (4916d659)

• Archived upstream in April 2026 (see issue [audit] nvim-treesitter query files frozen at archival — TSSync latest parsers will diverge #63 for full analysis)
• No further updates expected; the pinned commit is effectively the final version
• Action: no update needed; focus on the migration path described in [audit] nvim-treesitter query files frozen at archival — TSSync latest parsers will diverge #63

nvim-lspconfig (246572944)

• require('lspconfig') framework is deprecated; v3.0 will remove it
• Config already uses vim.lsp.config[] / vim.lsp.enable() directly — no action needed
• nvim-lspconfig now primarily ships server config files consumed by the built-in API; keeping it updated ensures new server definitions (e.g. pyrefly — see [audit] vim.lsp.enable("pyrefly") silently no-ops — missing vim.lsp.config registration #56) become available

Medium priority

conform.nvim (18aeab3d)

• Active releases; lsp_fallback = true was deprecated in favour of lsp_format = "fallback" — config already uses the new form ✓
• Check for new formatter support (ruff, biome, etc.)

gitsigns.nvim (dd3f588b)

• Active development; adds inline hunk display, GitsignsUpdate autocmd, linematch diff support
• Minimal gitsigns.setup() call means updates are low-risk

fzf-lua (3ff77862)

• Active development; no reported breaking changes in the current pinned range
• ctrl-alt-h toggle-hidden action used in config — verify it still works after update

nvim-treesitter-textobjects (851e865)

• Post-archival of nvim-treesitter, textobjects is independently maintained
• See issue [audit] nvim-treesitter-textobjects: tso.setup({ move }) set_jumps may be silently ignored #72 for a potential set_jumps regression

Low priority (stable / cosmetic)

Recommended action

1. Update obsidian.nvim to v3.14.0 and verify the minimal config still works
2. Update nvim-lspconfig to pick up new server definitions (especially pyrefly — [audit] vim.lsp.enable("pyrefly") silently no-ops — missing vim.lsp.config registration #56)
3. Update conform.nvim, gitsigns.nvim, fzf-lua in a batch — all are low-risk
4. Pin cosmetic themes to their latest tagged release for reproducibility
5. Leave nvim-treesitter at its current archived commit