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
Following paragraph from README.md says that even for resolving artefacts published to github package registry, it requires token with write package permission.
As an example, the documentation claims that, if you aren't publishing,
your token only requires the read: package grant (and not write: package).
Based on testing, as of right now, that appears to be false:
write: package is required for all API calls against GitHub Packages,
including resolution.
But seems like that is not the case anymore. I have tried publishing with default secrets.GITHUB_TOKEN using github action but was able to resolve using a token which has just read packages permission.
Just to quickly check, you can open up this url in browser and provide username: your github username password: Personal Access Token with just read packages permission
Following paragraph from
README.md
says that even for resolving artefacts published to github package registry, it requires token with write package permission.But seems like that is not the case anymore. I have tried publishing with default
secrets.GITHUB_TOKEN
using github action but was able to resolve using a token which has just read packages permission.Just to quickly check, you can open up this url in browser and provide
username: your github username
password: Personal Access Token with just read packages permission
https://maven.pkg.github.com/kpritam/gpr-playground/com/github/kpritam/gpr-playground/gpr-playground_2.13/1.0.3/gpr-playground_2.13-1.0.3.pom
The text was updated successfully, but these errors were encountered: