Release v0.9.0 · bngarren/checkmate.nvim

0.9.0 (2025-06-19)

config: no longer apply default metadata props to a modified default metadata in config (#95) User configs that relied on the 'default' metadata being merged in with their own will need to copy the default (see README). This is to avoid unexpected behavior from unrecognized merging.

improved keymapping config, deprecated checkmate.Action (#119) (899337b) (should integrate with which-key.nvim #118)
new features for metadata (#116) (116b272)
- provides a MetadataContext to metadata config functions such as get_value, style, and choices. This allows for more powerful, context-aware metadata customization
- new select_metadata_value with picker UI (or custom picker implementation) to easily fetch and select a metadata's value. See the choices option in the metadata properties
- Jump to next/previous metadata with new commands/api
simplify highlight groups and style configuration (#124) (ea73174)
updated user commands to use nested subcommands (#109) (8b87942)

Top-level user commands, e.g. :CheckmateToggle, :CheckmateArchive, etc. are deprecated. Instead, use :Checkmate [subcommand] syntax. Legacy commands remain for backwards compatibility but will be removed in next release.
checkmate.Action strings were previously used for mapping keys. These are deprecated and users should now use a checkmate.KeymapConfig which is a dict-like table or a sequence of {rhs, desc?, modes?}
checkmate.StyleKey strings were previously used in style to configure a hl_group. The new approach is to use checkmate.HighlightGroup which mirrors the actual name--removing this confusing layer of abstraction

config: no longer apply default metadata props to a modified default metadata in config (#95) (1d68a40)
fixes bugs with sync/async processing of metadata 'choices' fn (#121) (22a9157)
highlights: ensures treesitter markdown highlights are ON by default (#115) (d289ebe)
pre release fixes (d62dcb3)
various bug fixes (#117) (116b272)