Use GitHub Packages for our saf-cli binaries (exe and dmg and linux) and perhaps other common locations (brew, npm, etc)

[aaronlippold]

See: https://docs.github.com/en/packages

[Amndeep7]

@Rlin232 created a github action for brew, but it doesn't work lol. Fixed some of the issues it had, but currently running into an auth issue. The action we're using to do all the heavy lifting doesn't seem to support cross repository within same org commits without using a PAT. I wanna see if we can swap it out for other actions that might be able to get over the different repository divide. If not, then I'll ask the other admins if they think it would be alright with making a cross-org PAT that would have permissions to write to arbitrary repositories. Well, I think there are actually plenty of those already since any PAT generated has access to all the repos you have visibility into, but we don't (as far as I'm aware) stick them into the secrets section of a github repo.

I'm kinda doubtful that those other actions will be able to do it either, based off of my understanding of the permissions structure, but guess it can't hurt to try.

https://stackoverflow.com/questions/71068476/accessing-another-repository-with-github-cli-in-github-actions

[Amndeep7]

Regarding the PAT thing, might be a good feature request for GitHub to be able to scope PATs not just on generic permissions but also on a per org/repository level.