release new version of rockspec for Lua 5.5 support

[Tieske]

Since #33 the development rockspec is 5.5 compatible. But what is missing is a published 0.7.1-2 rockspec on LuaRocks (current is 0.7.2-1)

[hishamhm]

@Tieske the package is currently owned by the argparse user. Last time, @daurnimator did the release: 27967d7 — I think he might also have the credentials for the argparse user on LuaRocks.org?

[daurnimator]

@Tieske the package is currently owned by the argparse user. Last time, @daurnimator did the release: 27967d7 — I think he might also have the credentials for the argparse user on LuaRocks.org?

Apparently yes! It's sitting in my home dir for the last several years.

$ luarocks upload argparse-scm-2.rockspec
Sending argparse-scm-2.rockspec ...

Error: Revision scm-2 already exists on the server. See '/usr/bin/luarocks help upload'

$ luarocks upload argparse-scm-2.rockspec --force
Sending argparse-scm-2.rockspec ...

Done: https://luarocks.org/modules/argparse/argparse

[Tieske]

@daurnimator can you also upload a regular (non-development) rockspec? Since there are no code changes just reusing the 0.7.1-1 as 0.7.1-2 with 5.5 enabled, will do.

Alternatively it could also be transferred to LunarModules if you are up for that. Then I can take it from there.

[luau-project]

Since there are no code changes just reusing the 0.7.1-1 as 0.7.1-2 with 5.5 enabled, will do.

Based on the fact that argparse is quite popular nowadays, and that people fetch the source code in different ways (e.g.: LuaRocks, direct tarball download, git, etc), to cover the majority of users, in my opinion, I think it would be a good idea to push a new tag including a newer (non-dev) rockspec supporting Lua 5.5 even without code changes.

Alternatively it could also be transferred to LunarModules if you are up for that. Then I can take it from there.

An automated rockspec upload through GitHub workflows based on private LuaRocks API tokens would be really nice to minimize the dependency on daurnimator local setup, in case he agrees on that. It could be done transfering to LunarModules, or even through pull requests without transfering the module.

[daurnimator]

I'd prefer we tag an actual new release (0.7.2)

An automated rockspec upload through GitHub workflows based on private LuaRocks API tokens would be really nice to minimize the dependency on daurnimator local setup, in case he agrees on that. It could be done transfering to LunarModules, or even through pull requests without transfering the module.

Personally I'm not a fan of trusting github with publishing.
The module is currently owned by a special argparse org on luarocks so that we can grant that permission more granularly than lunarmodule.
I'm happy to let another couple of people into the argparse luarocks user and they can generate their own API keys.

[Tieske]

whether to move or not is a later concern I think. for now the most pressing need is an updated rock on luarocks, an 0.7.1-2.

[zenspider]

nudge. a proper release would really help. this is blocking luacheck and prolly many others