Prepare v13 tag for Lua 5.5.1 - #6
Conversation
* The latest Lua is 5.5.1. The 5.5 alias should resolve to Lua 5.5.1; * Only keep Lua 5.1 (for historical reasons) and Lua 5.5 aliases in the matrix, removing previous Lua 5.4; * LuaJIT has removed all previous tags. Due this change, it is not possible to install earlier versions anymore (LuaJIT 2.0.3, LuaJIT 2.0.5 or LuaJIT 2.1.0-beta3).
* LuaJIT all the previous tags from the GitHub repository. For this reason, it is pointless to keep entries for that tag in the source code.
* Use Lua 5.5.1 as latest version; * Remove references to previous tag versions from LuaJIT examples (LuaJIT tags were removed); * Update `luarocks/gh-actions-lua` from `v12` to `v13`.
| "url": "https://github.com/luajit/luajit.git", | ||
| "branch": "v2.1.0-beta3", | ||
| "binary": "luajit-2.1.0-beta3" | ||
| }, |
There was a problem hiding this comment.
This one could be a breaking change for people. But I assume they could change it to luajit-2.1 and get (mostly?) equivalent behavior.
There was a problem hiding this comment.
trying to install LuaJIT 2.1.0-beta3 was failing for users as well (see lunarmodules/copas#197).
There was a problem hiding this comment.
Yep, deleting tags is a pretty nuclear option for making people upgrade.
But the Lua community, ever since the Lua/LuaJIT split around 5.2 (gosh, that was... 15 years ago!?), has gotten in this paralyzing tendency of supporting old versions forever, even when upstream doesn't support them anymore. We should really be (gradually?) moving into supporting only the latest PUC-Rio Lua and the latest LuaJIT, at best.
If people want to be using very very old versions of Lua, they should be using very very old versions of the supporting ecosystem as well, and not forcing maintainers into supporting 20+ years of legacy at all times.
|
Since everyone seems to agree that these changes are ok, I'll proceed to push a new tag here, and also submit a PR in the other repo to update subsequent docs (only this repo will have a new tag). The other repo just needs to have the docs up-to-date referencing the version here. |
4 participants
Description
CC @hishamhm
A set of changes to prepare a new tag (
v13) for the repo, updating versions on both CI and docs.Note
In the absence of admin reviews, I'll merge it in a week (7 days). Otherwise, I can merge and publish a new version as soon as there is enough agreement that these changes are ok.
Changes
5.5.1;luajit-2.0.3,luajit-2.0.5andluajit-2.1.0-beta3from bothmain.js, CI workflows and docs.Important
The reason for the removal of these LuaJIT versions was because Mike Pall deleted all the previous LuaJIT tags (see https://github.com/LuaJIT/LuaJIT/tags/). So, it is pointless to have references to such versions in code, CI and docs.