A mirror of https://github.com/luarocks/luarocks.git https://git.lua4.win/luarocks/atom?h=test-pin 2025-06-30T15:17:42+00:00 2025-06-30T15:17:42+00:00 Luau Project luau.project@gmail.com 2025-06-30T15:17:42+00:00 urn:sha1:b45502ab0f1b7e1a02313036f115c213c8ee0ef9 On every tagged release of LuaRocks, there is the need to update LuaRocks version at [https://github.com/luarocks/gh-actions-luarocks/blob/22fa5618dc4ddff1fb251b3b38a0766a8c9ae47f/action.yml#L13](https://github.com/luarocks/gh-actions-luarocks/blob/22fa5618dc4ddff1fb251b3b38a0766a8c9ae47f/action.yml#L13) in the repository [https://github.com/luarocks/gh-actions-luarocks](https://github.com/luarocks/gh-actions-luarocks). Often forgotten, the default LuaRocks version on `gh-actions-luarocks` may lag behind the latest LuaRocks release. Motivated by this comment [https://github.com/luarocks/gh-actions-luarocks/pull/7#issuecomment-2997223378](https://github.com/luarocks/gh-actions-luarocks/pull/7#issuecomment-2997223378), to address this problem, incorporating the changes on this pull request, a new workflow was created to proceed in the following manner: 1. Once a tag is pushed (in the usual format `vX.Y.Z`) on [https://github.com/luarocks/luarocks](https://github.com/luarocks/luarocks), or in a manual workflow triggered by the tag ref, a sanitization step is performed to extract `X.Y.Z` from the `vX.Y.Z` in the job `SanitizeVersion`; 2. In a subsequent job (`CreatePullRequest`), a PR is created at [https://github.com/luarocks/gh-actions-luarocks](https://github.com/luarocks/gh-actions-luarocks) replacing the outdated version by the value `X.Y.Z` extracted earlier.