Release 2.1.0 is missing from jitpack.io

[marshalium]

Started seeing this error recently:

* What went wrong:
Configuration cache state could not be cached: field `compileTimeDependencies` of task `:app:dataBindingMergeDependencyArtifactsDebug` of type `com.android.build.gradle.internal.tasks.databinding.DataBindingMergeDependencyArtifactsTask`: error writing value of type 'org.gradle.api.internal.artifacts.configurations.ResolutionBackedFileCollection'
> Could not resolve all files for configuration ':app:debugCompileClasspath'.
   > Could not find com.github.SmartToolFactory:Compose-Extended-Gestures:2.1.0.
     Required by:
         project :app

2.1.0 is still listed in the index:

% curl https://jitpack.io/com/github/SmartToolFactory/Compose-Extended-Gestures/
1.0.0/
1.1.0/
1.2.0/
2.0.0/
2.1.0/
3.0.0/
3.1/
4.0.0/

But the 2.1.0 directory is missing:

% curl https://jitpack.io/com/github/SmartToolFactory/Compose-Extended-Gestures/2.1.0/
Not found

Other releases do exist. Here's the 2.0.0 directory still existing:

% curl https://jitpack.io/com/github/SmartToolFactory/Compose-Extended-Gestures/2.0.0/
Compose-Extended-Gestures-2.0.0-sources.jar
Compose-Extended-Gestures-2.0.0.aar
Compose-Extended-Gestures-2.0.0.aar.md5
Compose-Extended-Gestures-2.0.0.aar.sha1
Compose-Extended-Gestures-2.0.0.module
Compose-Extended-Gestures-2.0.0.module.md5
Compose-Extended-Gestures-2.0.0.module.sha1
Compose-Extended-Gestures-2.0.0.pom
Compose-Extended-Gestures-2.0.0.pom.md5
Compose-Extended-Gestures-2.0.0.pom.sha1
build.log

Seems likely that it's related to this bug where other jitpack.io users report releases disappearing randomly: jitpack/jitpack.io#5973

[SmartToolFactory]

Maybe i should start moving to maven as other authors mentioned in the thread

[SmartToolFactory]

How about latest release 4.0.0? I updated to latest version of Compose with the latest version

[marshalium]

4.0.0 is still available and looks like it will work for us

[jensck]

Maybe i should start moving to maven as other authors mentioned in the thread

Moving to Maven is a great idea. Jitpack's randomly disappearing artifacts seems like a deal-breaker, since their whole purpose is to distribute artifacts. I've never heard of this happening with Maven Central.