Jitpack LOST a build

[MFlisar]

Describe the bug One old version build of one of my libraries suddenly got lost... I know it did work in the past because I used this version quite some time myself.

To Reproduce Steps to reproduce the behavior:

1. Open https://jitpack.io/com/github/MFlisar/CacheFileProvider/
2. You will see it has a build for 0.2
3. Try to open https://jitpack.io/com/github/MFlisar/CacheFileProvider/0.2/
4. You will get a "Not found" error

Expected behavior The old build should still be available

[gchallen]

I'm seeing failed requests for both old and new builds. Fairly random: some artifacts load, others don't.

After years of using Jitpack I'm moving my projects to Maven Central. Huge PITA, but I feel like Jitpack reliability has worsened recently.

[riddancegd]

I'm also experiencing this issue. Our app uses CacheFileProvider 0.2 and we are unable to build without this dependency. I would love to have a solution for this.

[MFlisar]

In the meantime the build did vanish completely and trying to open the log file did trigger a rebuild... sadly it does not build anymore because the used gradle version to build the library is not the same anymore as in the past (I assume). Sadly I did not define a gradle wrapper back then when I wrote the problematic version...

Nevertheless, the successful build did vanish for no reason...

[qinwang1023]

I would be very grateful if this issue is resolved.

[github-actions[bot]]

This issue is stale because it has been open for 30 days with no activity.

[MFlisar]

This seems to be a bigger issue, I jsut wanted to comile another old oroject of mine, updated gradle from 7 to 8 and tried to compile it and following can not be found anymore:

• https://jitpack.io/com/github/MFlisar/Lumberjack/lumberjack-viewer/5.2.5/lumberjack-viewer-5.2.5.pom
  • although lumberjack-viewer is listed under https://jitpack.io/com/github/MFlisar/Lumberjack/ trying to open https://jitpack.io/com/github/MFlisar/Lumberjack/lumberjack-viewer does not work

Same for https://jitpack.io/com/github/MFlisar/MaterialPreferences/screen-input/0.5.4/screen-input-0.5.4.pom

And the issue occurs for all modules that belong the respectve library...

[memoeslink]

Yeah, I have some missing builds as well.

[github-actions[bot]]

This issue is stale because it has been open for 30 days with no activity.

[github-actions[bot]]

This issue was closed because it has been inactive for 14 days since being marked as stale.