Versions 0.99.5 and 1.0.0

[jalvesaq]

I think we can release version 0.99.5 now, or after merging the pull request that improves latexmkrc detection, and then schedule the release of version 1.0.0 a few days/weeks later.

Suggested changelog for 0.99.5:

New features:

• Support for RTypst.
• Support for SQL chunks.

Changes:

• Search for latexmk in more places.
• Require R 4.1.0.
• Bug fixes.

Authors:

• Philippe Massicotte (@PMassicotte)
• Yun Jiang (@jiangyun-fun)
• Tod Morrison (@todmorrison)
• Urtzi Enriquez-Urzelai (@urtzienriquez)

[jalvesaq]

For version 1.0.0, I would like to remove the section Transitioning from Vim-R (Nvim-R). We could copy its contents to either a new Markdown document in the doc directory or to the release notes for 1.0.0. Creating a new document has the disadvantage of requiring maintenance. I prefer to move the information to the release notes.

[jalvesaq]

Should we replace nvim-treessiter with tree-sitter-manager in the README and Wiki examples?

Should we replace lazy.nvim with vim.pack in the README and Wiki examples?

[PMassicotte]

Should we replace nvim-treessiter with tree-sitter-manager in the README and Wiki examples?

Should we replace lazy.nvim with vim.pack in the README and Wiki examples?

I think we can mention both? A note that nvim-treessiter is archived, but still working. For plugin installation, I understand tha vim.pack is new to the latest version of nvim?

[jalvesaq]

You are right; there is an open issue on Neovim about upstreaming nvim-treesitter (issue 39006).
And yes, vim.pack works with Neovim >= 0.12.

[PMassicotte]

Good with me then :) the 1.0.0 milestone is good ;)

[jalvesaq]

Many projects have a freeze period before a stable release. What do you think of freezing R.nvim for four weeks? We could schedule the release of 1.0.0 for July 05 (Sunday), about 13:00 UTC. Until then, we would merge only pull requests fixing bugs, not new features.

[PMassicotte]

That is a very good idea. All good with me!