[deps] gitsigns.nvim v1.0.0 + v2.0.0 breaking changes — review before next SyncPkgs

[stanfish06]

What

gitsigns.nvim has had two major releases since the commit pinned in nvim-pack-lock.json (25050e4):

• v1.0.0 — released 2025-02-07
• v2.0.0 — released 2025-09-26

The current config calls gitsigns.setup() with no arguments, which avoids most migration pain, but two changes deserve explicit review.

Where

lua/config/plugin_config.lua:203–205 (gitsigns setup)
nvim-pack-lock.json (pinned rev 25050e4)

Breaking changes

v1.0.0

• Several functions deprecated (exact names not yet documented externally; check :checkhealth gitsigns on update)
• config.signs.* highlight groups deprecated — highlight groups should no longer be set via the signs config table
• current_line_blame_formatter_opts removed (not used here — safe)
• yadm support removed (not used here — safe)
• Blame filetype identifier changed: dots → dashes (affects any autocmd keyed on the blame filetype)

v2.0.0

• Custom highlight names in config removed entirely
• setup() is now optional — the plugin auto-initialises; calling gitsigns.setup() with no args still works but is equivalent to require("gitsigns") and is now redundant
• Minimum Neovim version bumped to 0.11 (already met by this config)

Why it matters

The no-args gitsigns.setup() call is safe across both versions. However:

1. nav_hunk("next") / nav_hunk("prev") in plugin_config.lua:215,222 — verify the function signatures haven't changed in v2.0.0
2. vim.b.gitsigns_head in statusline.lua:32 — verify the buffer variable name is unchanged

Recommended action

1. Run :SyncPkgs to update to latest gitsigns
2. Run :checkhealth gitsigns and check for deprecation warnings
3. Confirm ]g/[g hunk navigation and vim.b.gitsigns_head still work
4. If clean, no code changes needed — just confirm and update nvim-pack-lock.json