Skip to content

chore(main): release 2.0.0#24

Merged
zuqini merged 2 commits into
mainfrom
release-please--branches--main--components--zpack.nvim
Jun 3, 2026
Merged

chore(main): release 2.0.0#24
zuqini merged 2 commits into
mainfrom
release-please--branches--main--components--zpack.nvim

Conversation

@github-actions

@github-actions github-actions Bot commented May 19, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

2.0.0 (2026-06-03)

⚠ BREAKING CHANGES

  • the options and commands listed above no longer work. Migrate to the replacements shown before upgrading to 2.0.0.
  • :ZPack with subcommands

Features

  • adopt Neovim plugin best practices (#23) (2f45de6)
  • close lazy.nvim parity gaps across lazy triggers (#27) (9ed473a)
  • lazy-parity: add defaults.lazy and defaults.version (#29) (d52f0dd)
  • lazy.nvim spec parity (pin/optional/dev/specs/build/reload/sync) (#28) (b6f82cd)
  • remove deprecated features for 2.0.0 (#25) (4681a74)
  • support bang on :ZPack update/restore; document 0.13 native commands (4f9b312)
  • sync state with vim.pack via PackChanged on plugin removal (0b65048)

Bug Fixes

  • address PR #21/#22 review follow-ups (c9c6c61)
  • command-specific legacy command deprecation notice (8970a43)
  • correct bang placement in usage hints; always warn on legacy commands (2f4bf35)
  • guard non-number priority and non-string import field (af3f109)
  • guard non-string src/url/dir in normalize_source (b127f63)
  • harden lazy-load path against operator-pending loss + throw-leaks (#26) (c6079d5)
  • preserve typeahead order on multi-key sequences (6b99fcb)

Code Refactoring

  • :ZPack with subcommands (d197fc6)

This PR was generated with Release Please. See documentation.

@github-actions github-actions Bot force-pushed the release-please--branches--main--components--zpack.nvim branch 5 times, most recently from 9dc7092 to b877c9c Compare May 25, 2026 20:40
@github-actions github-actions Bot force-pushed the release-please--branches--main--components--zpack.nvim branch from b877c9c to 6074737 Compare May 27, 2026 02:41
@github-actions github-actions Bot force-pushed the release-please--branches--main--components--zpack.nvim branch from 6074737 to 459b24a Compare June 3, 2026 22:16
release-please generated a dangling BREAKING CHANGES note ('the options listed above ... replacements shown') because the PR-body table did not carry into the commit footer. Replace it with the real migration table and add a durable 'Upgrading from 1.x to 2.0' section to docs/tips.md (linked from README Tips & Migration).
@zuqini zuqini merged commit 1a5a7f2 into main Jun 3, 2026
4 checks passed
@github-actions

github-actions Bot commented Jun 3, 2026

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant