luarocks/.github/workflows, branch test-pin A mirror of https://github.com/luarocks/luarocks.git https://git.lua4.win/luarocks/atom?h=test-pin 2026-03-16T22:31:35+00:00 ci: bump OpenSSL to 3.6.1 2026-03-16T22:31:35+00:00 luau-project luau.project@gmail.com 2026-03-06T22:43:39+00:00 urn:sha1:e4689642f1b72efd221a60fd364efb5ce86eeff5 ci: test the build of LuaRocks binaries for Windows 2026-03-16T22:31:35+00:00 luau-project luau.project@gmail.com 2026-03-06T22:21:48+00:00 urn:sha1:aaa828ea1a71af131a78de61ce89643940da05dd .github/workflows: bump openssl version 2025-12-23T06:13:04+00:00 daurnimator quae@daurnimator.com 2025-12-23T06:13:04+00:00 urn:sha1:ddb1c93bf93c9774cb9d854a665d51c369ea5acd This should fix our CI failure chore(ci): use a released LuaRocks version 2025-07-27T07:05:00+00:00 luau-project luau.project@gmail.com 2025-07-23T00:02:45+00:00 urn:sha1:015e587d76729a18d4ad9456a77c6fc5dfeb772a chore(ci): bump OpenSSL to 3.5.1 and improve error message. 2025-07-27T07:05:00+00:00 luau-project luau.project@gmail.com 2025-07-22T23:59:02+00:00 urn:sha1:1e4f8d02618311cfb7a94344c5da809c78c9afd8 fix(ci): GitHub Actions yaml lint issues 2025-07-27T07:05:00+00:00 luau-project luau.project@gmail.com 2025-07-22T23:56:27+00:00 urn:sha1:0f1613be8536a17bf7bf47b83e294c841d36333f ci: automate PR to update LuaRocks version on gh-actions-luarocks (#1808) 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. chore: move to luarocks/gh-actions-luarocks 2025-06-05T14:41:33+00:00 bzp2010 bzp2010@apache.org 2025-06-05T04:10:37+00:00 urn:sha1:7c3a2ec75e970a701ed0aa0728998270d73b40aa fix: use specific luarocks version 2025-06-05T14:41:33+00:00 bzp2010 bzp2010@apache.org 2025-06-04T02:38:23+00:00 urn:sha1:7b9ccdc7ff9587bfdf5efbe0e7dd0f3b66a0e84d ci(windows): change zlib download url 2025-03-23T21:03:35+00:00 luau-project luau.project@gmail.com 2025-03-23T18:45:18+00:00 urn:sha1:7ed653f010671b3a7245be9adcc70068c049ef68