Open alpex92 opened 3 years ago
I think based on the discussion / plan here: https://github.com/sbt/sbt/issues/6294 We might be covered for already published versions since this is listed in the sbt-community plugin's @gilandose can possible confirm.
eg: this resolves https://repo.scala-sbt.org/scalasbt/sbt-plugin-releases/com.gilcloud/sbt-gitlab/scala_2.12/sbt_1.0/
Future releases will need to be published somewhere else, and it seems like the guidance is to move to publishing to OSS Sonatype (Maven Central) instead
An update for anyone following this: the sbt
migration to the new jfrog repo finished last night and this plugin shows up there. (https://scala.jfrog.io/artifactory/sbt-plugin-releases/).
If you want to verify your projects can still resolve this plugin after the migration you can test it out like this: https://github.com/sbt/sbt/issues/6294#issuecomment-822506120
@gilandose will still need to find a new way to publish artifacts for future releases but any existing versions should now be safe for the next brownout and eventual end of service for bintray/jcenter
Bintray is scheduled to shut down at may 1st and currently not available at 12 april (service brown-outs to remind users about the services that are going away on May 1st.)
https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/
artifacts would not be available leading to CI/CD and fresh project failures
consider publishing artifacts somewhere else