-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
question re: luarocks packaging and releases #96
Comments
Yes, I need this as well, as currently the |
@zhuizhuhaomeng sorry to ping you directly, but is there anything that can be done about this? |
bump, there is already 2.1.0.13 tag, is it possible to publish new versions to luarocks.org? |
Great to see #84 by @hishamhm was merged. So all that's left is a new release and upload to LuaRocks. Anything we can do to facilitate @zhuizhuhaomeng ? |
@Tieske I didn't use the LuaRocks before? |
@zhuizhuhaomeng there is little to it, ensure you have Luarocks installed, and have the Apikey handy, then from the repo do:
|
There are also github actions that can automate this process, see https://github.com/lunarmodules/busted/blob/master/.github/workflows/deploy.yml |
@zhuizhuhaomeng any update on this? anything you need? |
I don't know how to find the email of the account "openresty". |
@hishamhm can you provide @zhuizhuhaomeng with the email address of the OpenResty LuaRocks account? |
@zhuizhuhaomeng I emailed the address to the gmail address that is in your Github account info. |
@zhuizhuhaomeng any update on this? |
Only merge this afetr the rockspecs for it have been fixed. See: openresty/lua-cjson#96
We've noticed the luarocks package of lua-cjson has not been updated in some time:
I'm aware the most up-to-date version is bundled with OpenResty itself, but many projects (resty-related and otherwise) take
lua-cjson
as a dependency.Is it possible to publish an updated package to luarocks? Perhaps this should come with a new tag/release as well, as there has been at least one important bugfix merged since 2.1.0.12.
The text was updated successfully, but these errors were encountered: