Breaking changes on main

[saecki]

This issue tracks the breaking changes on the main branch.

We follow the Conventional Commits specification, so breaking changes will always be marked with an !. If you use packer.nvim or lazy.nvim, they will be highlighted on update.

If you find breaking changes too disruptive to your workflow, the recommendation is to either follow the stable tag which should point to the most recent release, or even pin a release tag directly like v0.4.0.

[saecki]

#86 changes the way the nvim-cmp source is registered. It has to be manually enabled from now on.

require("crates").setup {
    src = {
        cmp = {
            enabled = true
        },
    },
}

If you have disabled autoload, you'll have to manually register the source. Note this requires nvim-cmp to be loaded.

require("crates.src.cmp").setup()