Goal I want to have two repositories: Repository A: Publishes a JAR to Github Registry Repository B: Downloads the JAR from A and publishes a Docker Image containing the JAR. I.e. I'm searchin...

GitHub packages started returning error pulling image configuration: unknown blob this weekend when trying to pull docker images. It still works to push images to the registry. I haven't found any ...

I am the maintainer of a public GitHub repo. I have set up GitHub Actions to build a publish to GitHub Packages. You can see the package has been created here: https://github.com/paulschwarz/sprin...

I'm having a hard time publishing a Java library in its 0.0.1-SNAPSHOT version to GitHub Packages. The library is a Gradle project. It would appear that, when the version is not on GitHub (yet), it...

I have pushed a Docker image on GitHub Packages and now I would like to pull it and use it. To run the image locally, I used to go to the related folder and run it with the command docker-compose u...

For my project, I am trying to install (not publish!) a npm package from GitHub Packages. It is hosted on a private repository, which is in an org. I have made a personal access token with the requ...

For various reasons we are stuck using yarn managing our packages so we can't rely on a package-lock.json to use npm with github actions. We cannot get Yarn to authenticate as part of a github act...

GitHub offers two options for storing container images as I understand it: Container Registry and Packages, but I think the difference is not clear. In a blog post, they say "With GitHub Actio...

There are a lot of similar issues already floating around: Install private github package from package.json on Github Actions Download private module from Github Package Registry via Yarn within ...

My build is working locally by using a User + PAT (personal access token) directly on the pom.xml <repository> element: <repository> <id>github</id> <name>GitHub Pac...

So, I have a GitHub project with a Package Registry configured. It has two packages: Package pages have instructions only for Maven, besides that, the instructions are broken (maven install so57...

I am trying to upload a Maven artifact I haven't built to my Organization's GitHub package registry. I am using the deploy:deploy-file Maven plugin in order to do so. Here is the command I have bee...

I'm trying to use Github's new Actions CI server to deploy packages to Github's new packages feature. It's not going well. I think it's all set up correctly, but I get this error: Failed to execu...

We have a monorepo with a shared package called "@myorganization/common", that is used by both the app and Google cloud functions. Google cloud functions requires that the package is publ...

Consider I have a maven plugin project and I want to publish it to Github's public maven repository called "Github Packages". I've done everything by instruction and for normal projects everything ...

I was trying to use the github packages, I followed all the steps in their basic tutorial, but I can't deploy, I already looked on several sites to fix this, but none worked. Error on deploy: Fail...

I'm looking for some comparison between this to registry, did anyone try both? Why I should use one or another? What are the pros and cons of each registry?

I have read the instructions on how to delete a version here: https://help.github.com/en/github/managing-packages-with-github-packages/deleting-a-package When I tried to use the curl, it just give...

Has anyone managed to get Maven dynamic version resolution working with GitHub packages? I want to be able to declare a dependency with a dynamic version and have it resolved, like this: depende...

I have a private repository under user X and repository name Y: https://github.com/X/Y This a Java project built with Gradle. The Gradle configuration file has been configured as explained in th...

This is sorta Q&A, I've put my solution in the answers. I'm part of both the GitHub Actions beta and the GitHub Package Registry beta. Since I'm a very lazy person I not only automated the bui...

I got access to the github package registry beta, just fiddled with it and followed the configuration steps to publish. The thing is, I published it correctly, but noticed it didn't publish to npm...