You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, it seems when using the GITUHB_TOKEN credential, the uploaded packages are associated with the repository of the workflow being run, and are only accessible to that repository. This is unfortunate, as the package repository is per organization, not per repository, so if another repository is setup with the same packages to cache, they can't both upload a package with the same name.
WARNING: Your request could not be authenticated by the GitHub Packages service. Please ensure your access token is valid and has the appropriate scopes configured.
Seems there is a new
vcpkg
feature designed specifically for GitHub Actions (though is still experimental):https://learn.microsoft.com/en-us/vcpkg/users/binarycaching#gha
In the past we've used the NuGet method, with setup for GitHub Actions:
https://learn.microsoft.com/en-us/vcpkg/users/binarycaching#quickstart-github
However, it seems when using the
GITUHB_TOKEN
credential, the uploaded packages are associated with the repository of the workflow being run, and are only accessible to that repository. This is unfortunate, as the package repository is per organization, not per repository, so if another repository is setup with the same packages to cache, they can't both upload a package with the same name.Sample workflow run error:
https://github.com/OutpostUniverse/op2-landlord/actions/runs/5395217904/jobs/9797427353
Relevant GitHub documentation:
Organization package settings:
Organization packages:
The text was updated successfully, but these errors were encountered: