ci: use LuaRocks action archive fix #393

Merged
barrettruth merged 1 commit from ci/use-luarocks-action-v0.1.3 into main 2026-05-03 18:30:43 +00:00
Owner

Problem

Nightly LuaRocks publishing is failing in the action test-install step because the generated scm rockspec rewrites the Forgejo HTTPS URL to the native git:// protocol. Forgejo is reachable over HTTPS, but the native git protocol times out because the VPS does not serve port 9418.

Solution

Use barrettruth/luarocks-tag-release-forgejo@v0.1.3, which keeps scm rocks on Forgejo archive URLs instead of rewriting them to git://.

Validation:

  • action repo nix flake check --accept-flake-config
  • action repo nix build --accept-flake-config .#luarocks-tag-release-action
  • action repo busted spec/rockspec_spec.lua with Nix Lua
  • cp.nvim workflow YAML parsed with PyYAML via Nix
  • git diff --check
## Problem Nightly LuaRocks publishing is failing in the action test-install step because the generated `scm` rockspec rewrites the Forgejo HTTPS URL to the native `git://` protocol. Forgejo is reachable over HTTPS, but the native git protocol times out because the VPS does not serve port 9418. ## Solution Use `barrettruth/luarocks-tag-release-forgejo@v0.1.3`, which keeps `scm` rocks on Forgejo archive URLs instead of rewriting them to `git://`. Validation: - action repo `nix flake check --accept-flake-config` - action repo `nix build --accept-flake-config .#luarocks-tag-release-action` - action repo `busted spec/rockspec_spec.lua` with Nix Lua - cp.nvim workflow YAML parsed with PyYAML via Nix - `git diff --check`
ci: use LuaRocks action archive fix
All checks were successful
quality / Test (pull_request) Successful in 8s
quality / Lint (pull_request) Successful in 9s
quality / Format (pull_request) Successful in 9s
7d50e9510e
barrettruth deleted branch ci/use-luarocks-action-v0.1.3 2026-05-03 18:30:43 +00:00
Sign in to join this conversation.
No description provided.