Skip to content

is it possible to tag releases on luarocks.org ? #267

Open

Description

@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.

Activity

  1. barrettruth commented on Sep 22, 2025

    @barrettruth
    Collaborator

    @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?

  2. teto commented on Sep 23, 2025

    @teto
    Author

    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

    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
  3. barrettruth commented on Feb 3, 2026

    @barrettruth
    Collaborator

    @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.

  4. barrettruth commented on Feb 5, 2026

    @barrettruth
    Collaborator

    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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions