Repository navigation
chore(main): release 3.0.0 - #48
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
force-pushed
the
release-please--branches--main--components--zpack.nvim
branch
3 times, most recently
from
October 31, 2026 08:00
8bf9cf7 to
9a09356
Compare
github-actions
Bot
force-pushed
the
release-please--branches--main--components--zpack.nvim
branch
2 times, most recently
from
November 2, 2026 20:13
240ced3 to
47c2382
Compare
github-actions
Bot
force-pushed
the
release-please--branches--main--components--zpack.nvim
branch
from
November 3, 2026 19:16
47c2382 to
139b76e
Compare
github-actions
Bot
force-pushed
the
release-please--branches--main--components--zpack.nvim
branch
from
November 6, 2026 05:23
139b76e to
4360718
Compare
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.
🤖 I have created a release beep boop
3.0.0 (2026-11-06)
⚠ BREAKING CHANGES
dependenciesoverrides a top-level one and its functionoptssees the top-level optsrequireloads a lazy plugin only when the plugin holds the module's file, as in lazy.nvim; one with only the top-level name stays lazy:ZPack cleanand:ZPack synclist what they would delete and ask, defaulting to No;!skips the promptnilin a spec list no longer ends the list, so what follows it installssetup({ profiling = ... })is ignored, andprint_profileandget_profileare gonerequireno longer loads a plugin whose name resembles a module it doesn't provide; a plugin registering a module fromplugin/needs a trigger of its ownkeysare two keys unless the second can only be an rhs, so{ '<leader>d', 'dd' }needs a field or nesting to stay one keyenabledorcondwins, instead of anyfalseeventwith no real event in it, such asLazyFile, leaves the plugin eager with a warningversionstring git can't take as a ref, such as*, is a semver rangeFeatures
Bug Fixes
:ZPack cleanand:ZPack synclist what they would delete and ask, defaulting to No;!skips the prompt (936649e):ZPack cleanleaves a plugin active this session for next time rather than raising (936649e)ftplugin'sftdetect/is sourced once, as in lazy.nvim, so one that runsset filetype=firesFileTypeonce per file (bfd84e3)initremoving a plugin no longer re-fires its event or crashessetup()when the plugin has its owninit(bfd84e3)nilin a spec list no longer ends the list, so what follows it installs (936649e)importwith no plugin of its own finds its module in a listed plugin named after it, installing it if missing, on the first start (936649e)lua/offpackage.pathafter startup (936649e)keyson the same lhs don't stop it loading (bfd84e3);and,) gets it (bfd84e3)keysare two keys unless the second can only be an rhs, so{ '<leader>d', 'dd' }needs a field or nesting to stay one key (85ba638)eventwith no real event in it, such asLazyFile, leaves the plugin eager with a warning (85ba638)optsthat throws is reported once and the plugin still loads without itsconfig, as in lazy.nvim, instead of staying pending (bfd84e3)configturned detection on gets itsftdetect/once, not twice (bfd84e3)plugin/script's error without failing the load (936649e)dependenciesoverrides a top-level one and its functionoptssees the top-level opts (bfd84e3)dependenciesloads eagerly (#49) (85ba638)specsare dropped (#49) (85ba638)enabledorcondwins, instead of anyfalse(85ba638)requireno longer loads a plugin whose name resembles a module it doesn't provide; a plugin registering a module fromplugin/needs a trigger of its own (936649e)requireloads a lazy plugin only when the plugin holds the module's file, as in lazy.nvim; one with only the top-level name stays lazy (241c9ba)requireof a module whose load threw raises that error instead of returningtrue(241c9ba)require('lspconfig/util')loads the pending plugin holding the module (241c9ba)vim.packdoes when deciding if one fits (936649e)#or%in the data path no longer fails with E194/E484 and loses the file (bfd84e3)setup()with nospecand nolua/plugins, or one holding only dotfiles, is quiet, as in 2.x (936649e)setup()'s options no longer count as spec fields, so specs written beside them all install (936649e){ import = ..., defaults = ... }, is read as a spec rather than ignored for the default import (936649e)setup('custom.plugins')and inspec, rather than reported and replaced by the default import (936649e)setup()argument that isn't a table is reported, and the default import goes on (936649e):colorschemeloads the pending plugin holding the scheme first, as in lazy.nvim, so a Vim colors file can call its plugin'sautoload/from aninitor for a lazy plugin, and an eager scheme plugin set from an earlier plugin'sconfig(themery.nvim's restore) gets its ownconfigfirst (bfd84e3)requirefrom aninitloads the eager plugin holding the module, as in lazy.nvim, instead of failing with "module not found" (bfd84e3)cmd,event,ftandkeysare set up before the inits, as in lazy.nvim, so aninitrunning one loads the plugin (bfd84e3)ftdetect/runs when filetype detection is on beforesetup(), as in lazy.nvim, so LazyVim's vimtex opens a.clsastex(bfd84e3)configonce when a lazy dependent loads it (936649e)versionortagof the wrong type is dropped with a warning instead of failing every plugin (936649e)versionstring git can't take as a ref, such as*, is a semver range (85ba638)sem_versionthat isn't a semver range, and fall through tobranchanddefaults.version(936649e)Performance Improvements
Code Refactoring
setup({ profiling = ... })is ignored, andprint_profileandget_profileare gone (936649e)This PR was generated with Release Please. See documentation.