@mattip - the example you showed in numpy-wheels seems to use a Travis secret not a GitHub org secret. Does this mean we have to switch to GitHub actions, or is there a way for Travis to access the secrets? And how should we deal with AppVeyor?

No, that is for github actions only. For each other CI you need to create specific secrets. I don't know who owns https://travis-ci.org/github/MacPython/astropy-wheels/ - whoever it is can see the "settings" option under the "more options" hamburger menu on the right and get to the secrets section. If whoever it is cannot already create a token on anaconda.org, I could add them. Or one of the people who can create tokens on anaconda.org could take over the CI on https://travis-ci.org/github/MacPython/astropy-wheels/.

Similarly for AppVeyor.

Alternatively, you could try moving to github actions. If you wish to release wheels for ARM64, the best option (in my opinion) is still travis, since github actions only runs x86.

Hi @mattip, could you please add me to the organization on anaconda.org so I can create the tokens ?
My username is "saimon" on anaconda.org

Could one of the core maintainers vouch for @saimn? I don't see anyone by that name as a committer here.

@mattip I vouch for @saimn!

I added him as an admin to this repo

Thanks. Done.

Thanks @mattip !

@mattip - would it be possible to add myself and @saimn to the AppVeyor project for astropy-wheels?

I added @saimn. Is there a problem creating the tokens?

@mattip - I could create the tokens on anaconda.org, and add them in Travis, but I don't have access to AppVeyor's admin interface. Do you know if something must be done to get this access ?

(I also can't access the AppVeyor admin interface)

I think @matthew-brett might know?

(another reason to move to github actions for all x86 builds)