Allow Teal types to be installed via LuaRocks

[FourierTransformer]

I was noodling on some options in teal-language/tl#1071 and have really taken to the idea of having the Teal type definitions (only - not dependency linked) available in LuaRocks. It will allow cyan to remain a little bit less dependency heavy, and in theory could be fully automated when someone merges to master in this repo.

I started working on this a little bit and think it could be split into a couple of PRs/sections:

• 1. Generating rockspecs (I have a PR ready for this part)
  • a script that generates rockspecs for each of the types and keeps track of the last git sha/files generated
  • initially manually run and uploaded rockspecs
• 2. GHA to upload rockspecs to LuaRocks
  • would need a LuaRocks api key setup as a secret in the repo from likely a new LuaRocks account
• 3. GHA on push-to-main that generates rockspecs, uploads, and updates this repo
  • would need a GitHub account that can open PRs in this repo

I'm willing to help write, maintain, and support as needed. Also, totally understand if this is not the direction you guys want Teal type definitions to go or if you just want to stick with the manual generation/upload process for now.

I'll put in the PR for step 1 here shortly.

[hishamhm]

would need a LuaRocks api key setup as a secret in the repo from likely a new LuaRocks account

The good news is that I reserved the "types" account for this purpose 5 years ago :) https://luarocks.org/modules/types

I just added a LUAROCKS_API_KEY for it in this repository's Actions secrets.

[hishamhm]

@FourierTransformer Types are uploading! \o/ https://github.com/teal-language/teal-types/actions/runs/21732977469

[FourierTransformer]

Also, looks like the SLAXML file failed. I'll put in a PR to get it resolved in a little bit (and update the README!)

[FourierTransformer]

Exciting to see them all finally in LuaRocks!

So, if we want to try automatic PRs we'd probably want an account with a Git PAT setup with all the right permissions, likely with a new account (and I feel like I probably shouldn't own that account...). I was thinking it would follow what is laid out in this SO post which includes some of the permissions needed in the comments.

Also, if you want to hold off going that far for now, I can roll up every now and again, run the generation script and manually put in a PR.

[hishamhm]

@FourierTransformer do you mean creating a new GitHub account to act as the upload bot, give it permissions to this repo, create a PAT for it, and add the PAT to this repo's secrets?

[FourierTransformer]

Yup! I think that should do it. The bot account would need read and pr permissions on this repo.

[hishamhm]

@FourierTransformer I created the teal-types-bot GitHub user and gave it access to this repo. I also created a GitHub PAT for it, and added it as the TEAL_TYPES_BOT_PAT environment to this repo.