Suddenly started receiving 403 Forbidden when fetching private packages in Github Actions #29019
Replies: 8 comments 7 replies
-
|
I got the same problem when I did: ➤ YN0027: my-package@unknown can't be resolved to a satisfying range Do you have any aidea? |
Beta Was this translation helpful? Give feedback.
-
|
We had the same issue, sort of. We have no issue downloading packages from new package repositories, however, we have problems querying for package versions. What we found is that new package repositories do not have the Also, |
Beta Was this translation helpful? Give feedback.
-
|
In my case the issue was the billing limit,
|
Beta Was this translation helpful? Give feedback.
-
|
I just ran into this. For me the problem was that I had set some permissions incorrectly in my job. permissions:
id-token: writeThis The fixed yaml: permissions:
id-token: write
+ contents: read |
Beta Was this translation helpful? Give feedback.
-
|
I'm running into this issue. I already have |
Beta Was this translation helpful? Give feedback.
-
|
I am running into the same issue. Locally the installation of the package works fine, no problems with any billing limits, but on jenkins the |
Beta Was this translation helpful? Give feedback.
-
|
For me it happened for a pkg only but not for others $ yarn install v1.22.22 |
Beta Was this translation helpful? Give feedback.
-
|
Have you folks found any solution? We have started getting the same error out of the blue (different library), without us changing any of our Github Actions configuration. Maven Central (where the dependency is fetching from) does not show any issues + we can build locally without any issues. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
Today we suddenly started receiving 403 Forbidden when installing private packages in an action:
error An unexpected error occurred: "https://npm.pkg.github.com/download/<our-org>/<package-name>/<version>/c465454e5b804aedd348669764fb1bc7ae6a68ec: Request failed \"403 Forbidden\"".The issue only occurred for a new package published today and we noticed that Github recently (have not seen it before at least) has extended package settings in order to define permissions for packages. However, when updating the permissions to match previous packages we are still getting the 403 from actions.
Locally we are able to install the packages but for some reason the standard
GITHUB_TOKENor${{ github.token }}does not have the right permissions. (The GitHub token has the default permissions read/write permissions on the organization level.)Beta Was this translation helpful? Give feedback.
All reactions