@HeEAaD Thanks for the detailed report. This is a legitimate gap in SwifterPM’s authentication handling.
SwifterPM has two separate auth code paths: one for registry packages (RegistryAuthorization) which does read macOS Keychain internet passwords, and one for binary artifact downloads (HTTPAuthorization) which does not [1] [2]. So your Keychain credentials are simply never consulted when downloading binary targets.
Workaround: You can authenticate private binary artifact downloads using either:
-
A
.netrcfile (~/.netrc) with your GitHub credentials:machine api.github.comlogin <your-username>password <your-personal-access-token> -
The
GITHUB_TOKENorGH_TOKENenvironment variable (automatically picked up forgithub.com/api.github.comhosts) [3]. -
Having the GitHub CLI (
gh) authenticated — SwifterPM will callgh auth tokenas a fallback.
Any of these should unblock you while this issue is addressed.
To reply, just mention @dosu.
Share context across your team and agents. Try Dosu.