Mismatch between blink.lib and blink.pairs

[MrZLeo]

Using blink.lib from main with blink.pairs v0.6.0 causes Neovim to fail during startup:

Error in /Users/mrzleo/.config/nvim/plugin/03-blink.lua:
E5113: Lua chunk: ...core/opt/blink.pairs/lua/blink/pairs/config/mappings.lua:40: attempt to call field 'catchall' (a nil value)
stack traceback:
        ...core/opt/blink.pairs/lua/blink/pairs/config/mappings.lua:40: in main chunk
        [C]: in function 'require'
        ...ack/core/opt/blink.pairs/lua/blink/pairs/config/init.lua:8: in main chunk
        [C]: in function 'require'
        .../site/pack/core/opt/blink.pairs/lua/blink/pairs/init.lua:22: in function 'setup'
        /Users/mrzleo/.config/nvim/plugin/03-blink.lua:86: in function 'setup_blink_pairs'
        /Users/mrzleo/.config/nvim/plugin/03-blink.lua:90: in main chunk

While using main branch of blink.pairs require user to build the plugin locally. This may be noisy maintaining Rust toolchain every update since blink plugin set always prefer better features from nightly. And for the case like remote development making it harder to build the plugin ourself.

I think there are two ways to resolve this:

1. provide tip release for blink.pairs
2. provide version release of blink.lib.

From my point of view, first option may be a better choice. But if there is another tradeoff, I can literally accept that.

I really appreciate the quality of blink plugins and the efforts you have made!

[saghen]

Made a release of blink.pairs (v0.7.0) to alleviate the issue for now. But you're right that we need a better long-term solution. I'll keep this open until we've figured something out.