Repository navigation
[deps] bump async.nvim, gitsigns.nvim, mini.nvim, nvim-treesitter, tinted-vim, tree-sitter-d2, vimtex pins - #349
Draft
stanfish06 wants to merge 1 commit into
Draft
stanfish06 wants to merge 1 commit into
stanfish06 wants to merge 1 commit into
Conversation
…ted-vim, tree-sitter-d2, vimtex pins Trivial, non-breaking drift verified via git log on each upstream range: - async.nvim: 1 commit, internal fix (fail tasks when await callbacks are discarded) - gitsigns.nvim: 2 commits, bugfixes (show_deleted rendering, detached-worktree git cwd) - mini.nvim: 4 commits, 1 fix (mini.pick noautocmd) + docs typos + 1 additive icon - nvim-treesitter: 1 automated parser-version bump commit - tinted-vim: 1 automated colorscheme-data refresh commit - tree-sitter-d2: 2 commits, a merged PR and a README example fix (no source changes) - vimtex: 4 commits, all to the plugin's own dev tooling (mise.toml deps), no source changes No `!` (breaking) conventional-commit markers and no feat/fix touching code paths this config exercises. blink.cmp and fff.nvim are intentionally pinned to older exact releases (see #271, #344) and are excluded; obsidian.nvim has a non-trivial actions.lua refactor in its drift range and is called out separately in the tracking issue instead of bumped here. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017S2hK7WgoBBKTgCHQ919AZ
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Scheduled dependency check against the current
nvim-pack-lock.jsonpins, viagit ls-remote+ commit-range review of every plugin (same method as #343/#345). Bumps 7 pins whose upstream drift since the last check is verifiably trivial/non-breaking:async.nvim15f28ec3→4182ab36gitsigns.nvimfd780920→d4854fa9show_deletedrendering; fix: git cwd for detached worktreesmini.nvima6e23131→ed868352mini.pickdropsnoautocmdon floating win; 3× docs typo + 1 additive iconnvim-treesitter29212d82→a2f69447tinted-vim20b38956→44b94ba5tree-sitter-d220043461→7bba2822vimtex79a5fb44→02eee260mise.tomldev-tooling dependency bumps only (no plugin source touched)Why it matters
Keeps these pins from drifting further behind upstream bugfixes while the drift is still small enough to review commit-by-commit. None of the above carry a
!(breaking) conventional-commit marker, and none touch a code path this config'splugin_config.luaexercises (no custommini.pick/gitsignsoptions beyond what's already set up, no treesitter parser list changes, no vimtex Lua config).Explicitly excluded from this bump (see tracking issue)
blink.cmp,fff.nvim— intentionally pinned to an exact older release (version = vim.version.range(...)); upstreamHEADdrift is expected and already tracked ([deps] fff.nvim at 0.9.6 (config targets 0.9.4); blink.cmp v2 imminent with breaking config changes #271, [deps] mini.nvim breaking changes upstream + audit corrections (Oct 2026) #344).obsidian.nvim— drift range includes a real refactor (feat(action): normal mode link and link_new and better link api, 284-line change toactions.lua/api.lua). Not unsafe for this config's minimal setup, but not "trivial" either — flagged in the tracking issue for a deliberate look rather than bundled into a mechanical bump.fzf-lua,nvim-lspconfig— already have an open, unmerged bump in [deps] bump fzf-lua, nvim-lspconfig pins: additive/docs-only #343 (whichnvim-lspconfigis now already fully satisfied by onmaster, andfzf-luahas since drifted 5 more commits past [deps] bump fzf-lua, nvim-lspconfig pins: additive/docs-only #343's target). Noted in the tracking issue instead of opening a competing PR.Recommended action
Merge as-is; recommend a quick
:checkhealth/ smoke-test ofmini.pick,gitsigns, and treesitter highlighting after merge given these touch UI-adjacent code paths, even though the diffs are small.Generated by Claude Code