You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A few years ago, I PRd a workflow that uploads nvim-cmp to luarocks when a tag is released.
Since then, we've developed rocks.nvim, which makes it easy to install plugins from luarocks for neovim (making it the developer's responsibility to declare dependencies, not the users').
Because no new tags have been pushed since then, the luarocks package is now quite outdated.
A potential long term solution to automate release tags could be #906 (I've had positive experiences with the release-please workflow).
Another option (if you don't want to commit to semver releases) would be to delete the existing package and to publish the luarocks package with version: scm instead. However, in this case, any package that depends on this plugin (I don't know how likely that is) would not be able to use semver releases, because luarocks won't search the dev manifest by default.
The text was updated successfully, but these errors were encountered:
Hey 👋
A few years ago, I PRd a workflow that uploads nvim-cmp to luarocks when a tag is released.
Since then, we've developed rocks.nvim, which makes it easy to install plugins from luarocks for neovim (making it the developer's responsibility to declare dependencies, not the users').
Because no new tags have been pushed since then, the luarocks package is now quite outdated.
A potential long term solution to automate release tags could be #906 (I've had positive experiences with the release-please workflow).
Another option (if you don't want to commit to semver releases) would be to delete the existing package and to publish the luarocks package with
version: scm
instead. However, in this case, any package that depends on this plugin (I don't know how likely that is) would not be able to use semver releases, because luarocks won't search thedev
manifest by default.The text was updated successfully, but these errors were encountered: