Github Packages and Gradle Failing

My actions builds (gradle script) started to fail fetching maven artifacts from Github.
Since yesterday evening…

> Could not resolve all files for configuration ':compileClasspath'.

[34](************/runs/2311728509?check_suite_focus=true#step:3:34) > Could not find ****:*******:1.2.12-SNAPSHOT.

[35](************/runs/2311728509?check_suite_focus=true#step:3:35) Searched in the following locations:

[36](************/runs/2311728509?check_suite_focus=true#step:3:36) -************/1.2.12-SNAPSHOT/maven-metadata.xml

[37](************/runs/2311728509?check_suite_focus=true#step:3:37) -************/1.2.12-SNAPSHOT//**********--1.2.12-SNAPSHOT.pom

[38](************/runs/2311728509?check_suite_focus=true#step:3:38) -************/**/************/1.2.12-SNAPSHOT/maven-metadata.xml

[39](************/runs/2311728509?check_suite_focus=true#step:3:39) -************/***/************/1.2.12-SNAPSHOT/**********-1.2.12-20210410.072648-1.module.pom

It seems that indeed the **********-1.2.12-20210410.072648-1.module.pom file does not exists
However **********-1.2.12-20210410.072648-1.module exists
and **********-1.2.12-20210410.072648-1.pom also exists

I am using GitHub packages and the same gradle script since 2 years and didn’t had such issues.

Any ideas ?


We have been looking more in detail and actually the maven-metadata.xml file that is on GitHub does not match the one that is generated by gradle when publishing locally.

It seems that GitHub is generating automatically the meta file from the content of the directory and that while having locally
< snapshot>
< timestamp>20210411.011638</ timestamp>
< buildNumber>1</ buildNumber>
</ snapshot>
GitHub generates
< snapshot>
< timestamp>20210411.011638</ timestamp>
< buildNumber>1.module</ buildNumber>
</ snapshot>
So yes it looks like an issue on GitHub side, someone probably pushed an update that forgot to remove the file extension to compute the build number…

Any update on this? We are also facing the same.

To further iterate, this is definitely some breaking change on GitHub - we are in the process of migrating our repositories to artifactory, and this fixes the issue for us. This will be a long migration, but we are currently left with no option as there seems to be no way in gradle to manage this - and I also have not received any response on the support ticket making this essentially an issue with an unbounded resolution time.

1 Like

I’m also facing similar issue since today (Monday, 2021-04-12), while all was working on Friday. In my case I have a maven repo with SNAPSHOTs. maven-metadata.xml has snapshot versions in form of 1.0-20210412.071823-1.pom, which is further resolved to which is not found.

1 Like

Facing the same issue as @vovencij with snapshot-artifacts in a maven-repo.

1 Like

Same issue here. Added a ticket on


Update: “This issue is currently affecting multiple GitHub customers, and our Packages engineering team are looking into it as a matter of urgency.”

I received a notification that the issue is fixed and my built passed!

The issue is indeed fixed and my build is now passing. Thanks!

Hey I’m not sure of how the effects are going but I’m trying to find out how to use some similar issues