Skip to content

chore(nvim): drop stale lazy-lock.json entries - #48

Closed
potsrevennil wants to merge 1 commit into
refactor/drop-nvim-lintfrom
chore/prune-lazy-lock
Closed

potsrevennil wants to merge 1 commit into
refactor/drop-nvim-lintfrom
chore/prune-lazy-lock

Conversation

@potsrevennil

Copy link
Copy Markdown
Owner

Stacked on #47.

The lockfile still pinned 16 plugins that no longer load: the dropped colorscheme/linting imports (catppuccin, tokyonight, nvim-lint), the removed bufferline spec, and the enabled = false stubs (noice, mason, mason-lspconfig, mini.ai/icons/pairs, lualine, grug-far, todo-comments, trouble, persistence, gitsigns). Lazy! restore already ignores them — they never load or fetch — so this is a hygiene pass to make the lockfile reflect reality.

This is a targeted 16-line deletion, not a :Lazy sync regeneration. A sync would bump all 31 surviving plugins to their latest upstream commits — exactly the moving-target churn lua/config/lazy.lua's restore-not-sync design avoids. Every surviving pin here is byte-identical to before.

  • Verify: CI Lazy! restore + smoke test resolves all 31 active plugins from the pruned lock.
  • Heads up (pre-existing, not addressed here): neo-tree.nvim is an active plugin but was already absent from the lockfile on master — its dep nui.nvim is pinned, neo-tree itself isn't. Fixing that needs a real regen (which bumps versions), so it's left for a separate decision.

Remove the 16 plugins the lockfile still pinned that no longer load:
the colorscheme/linting imports we dropped (catppuccin, tokyonight,
nvim-lint), the spec we removed (bufferline), and the enabled=false
stubs (noice, mason, mason-lspconfig, mini.ai/icons/pairs, lualine,
grug-far, todo-comments, trouble, persistence, gitsigns).

Targeted removal rather than a `:Lazy sync` regen on purpose: sync would
bump every surviving plugin to its latest upstream commit (the moving
target lua/config/lazy.lua's restore-not-sync setup exists to avoid),
whereas this keeps all 31 live pins byte-identical and only deletes the
dead lines. CI's `Lazy! restore` + smoke test verifies the pruned lock
still resolves every active plugin.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@potsrevennil

Copy link
Copy Markdown
Owner Author

Superseded by #49, which regenerates lazy-lock.json via :Lazy! sync instead of hand-pruning. Key learning: lazy.nvim keeps enabled = false plugins in the lockfile, so the manual removal here would have drifted from lazy's canonical output (a future sync re-adds them). #49 also fixes the neo-tree orphan and is the true in-sync state.

@potsrevennil
potsrevennil deleted the chore/prune-lazy-lock branch August 15, 2026 06:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant