is it possible to tag releases on luarocks.org ?

[teto]

none-ls is available at https://luarocks.org/modules/mochaap/none-ls.nvim .

I have some trouble with my none-ls version so I thought I would try a tagged stable version supposed to work to see if that was because I run a too recent version. Knowing that this tag works with neovim 0.11 and have the possibility to pin and go back to that is nice.
Alternatively I could use git directly but I like rockspecs with its automated dependencies handing.

[barrettruth]

@teto
are you able to write a pr for this? im remotely familiar with the luarocks ecosystem but you sound way more well versed. could u configure a pr so all we have to do is add the api key to the repository?

[teto]

right now, actions push an "scm" release a day to luarocks.

I could add another action that reacts to new tags but this repo doesn't seem to create tags.
What would you think to do as fzf-lua and create a luarocks release a day

• https://luarocks.org/modules/ibhagwan/fzf-lua
• https://github.com/ibhagwan/fzf-lua/blob/main/.github/workflows/luarocks-release.yaml

the version is not based on tags but on the number of commits. Since this repo doesn't contain dependencies, the only advantages of this for now would be for:

• rocks.nvim to be able to install it directly (without specifying the need for a "development" version)
• this makes compareasons between versions (when locking dependencies with a package manager) easier than with git shas

[barrettruth]

@mochaaP I plan to release a v0.1.0 in a PR. How does this sound to you?

I think this and manual luarocks updates for the plugin (I consider fzf-lua's approach a bit too "spammy") should be fine.

Will close when I push the tag.

[barrettruth]

sounds good to me. which format do you prefer?

• abseil style: YYYYMMDD.0 (e.g. 20260204.0)
• osu style: YYYY.DDD.0 (e.g. 2026.35.0)

also, should we keep the daily cron or only release when there are actual changes?