Hey @derongan, as far as I know we don’t support mutating packages in terms of publishing a new SNAPSHOT to override an existing SNAPSHOT.

@andreagriffiths11  Just to clarify, does this mean that we cannot upload multiple builds for the same snapshot (e.g. 1.0.0-SNAPSHOT) and have GitHub serve the latest artifact? Encountering a similar issue at the moment where only the first build is being pulled down from the repository (even after deleting my local cache). 

@jcansdale 

Hi, we publish snapshot packages with Gradle, it’s a plain .pom and .jar files. But unfortunately when we try to use snapshot package only first uploaded jar is downloaded. 

Also did try to publish packages with new Gradle module metadata files - and it’s the same, only first uploaded jar is downloaded. Do you know when snapshots will work in GitHub Packages ? thank you 

@derongan did you resolve you problem ? thank you 

Could you open a ticket here with a link to your repository any logs for publishing/consuming your package?

https://support.github.com/contact

Thanks,

Jamie.

Currently experiencing the same issue on a Gradle project, for some reason when multiple snapshots of the same version are uploaded (e.g. 1.0.0-SNAPSHOT), even when the cache for changing modules is disabled - explicitly set it to 0 seconds - GH Packages always returns the first artifact.

I thought it was a Gradle misconfiguration I made at first, but I can see in the logs that the resolved pom file is the one belonging to the first upload and any other dependency pulled from other Maven repos (not GH packages ones) with the same cache policy is always the latest.

Any chance this can get fixed? Thanks!

I opened a support ticket and got a confirmation today that the GH team is currently looking into the issue of the SNAPSHOT always returning the first version. I’ll post here again when I get updates.

Thanks for opening the ticket. A new version was deployed earlier today. This issue should now be fixed!

Works great now, thanks again!

Having the same problem here. Trying to publish a 0.0.1-SNAPSHOT artifact with Gradle. No error on the publishing side, but there’s no trace of the most recent artifact on GitHub. How do I solve this please?

Have the same problem here. Is this getting solved any time soon?

Still having the same issue, really frustrating as snapshots are really important for our development environment. I hope we hear back from the staff soon, switching back to our old repo in the meanwhile.

Yes, we had to move to Artifactory for that reason, which is a shame.

Same here. First I thought it was a mistake from my side, but after a couple of hours debugging it I can confirm the SNAPSHOT version is uploaded to Github Packages successfully but I can’t find it there or fetch the latest version.
I’m also using Gradle.

I managed to get it to work. A Maven project is publishing the package and I can see the new SNAPSHOT version on the GitHub package page under the Assets listing. The timestamps on the GitHub repo do not seem to change, which is a bit weird.

A Gradle project is importing the SNAPSHOT package, but do ensure that Gradle is not caching changing dependencies. Otherwise it might not download the latest version (even if you build with --refresh-dependencies). Edit gradle.build to include this:

configurations.all { resolutionStrategy.cacheChangingModulesFor 0, 'seconds' }

See https://stackoverflow.com/a/14804849/475511.