actions-marketplace-validations/LuaRocks tag release

Publish a package to LuaRocks when a new tag is pushed

Trust Signals

name	description	required	default
name	The name of the your package	yes	${{ github.event.repository.name }}
version	The version of your package. Uses the git tag by default (if one exists). Can also be set to `null`, `"scm"` or `"dev"` to publish a development rockspec.	no	${{ github.ref_name }}
specrev	The rockspec revision. Defaults to '1', resulting in <version>-1 as the <modrev>-<specrev>.	no	1
dependencies	List of LuaRocks dependencies.	no	—
test_dependencies	List of test suite dependencies.	no	—
labels	List of package labels.	no	—
copy_directories	List of additional directories to copy. Only directories that exist will be copied. The defaults are taken from Neovim's `:help runtimepath` WARNING: Do not add the directories `lua`, `lib` or `rock_manifest`.	yes	{{ neovim.plugin.dirs }}
summary	Short description of the package.	no	—
detailed_description	Detailed description of the package.	no	—
template	Path to a rockspec template.	no	—
license	The license SPDX identifier. By default, it will be fetched from GitHub. But sometimes, GitHub does not recognise it, in which case LuaRocks will fall back to this one.	no	—
extra_luarocks_args	Extra args to pass to the luarocks command. For example: "CURL_DIR=/usr/include/x86_64-linux-gnu/"	no	—
fail_on_duplicate	Whether to fail if the rock's version has already been published to `luarocks.org`.	no	—

no outputs