I updated compose from `1.2.0-alpha01-dev620` to `1.2.0-alpha01-dev675` and it isn't getting found. ...

# compose-desktop

[eygraber]

I updated compose from 1.2.0-alpha01-dev620 to 1.2.0-alpha01-dev675 and it isn't getting found. The latest version on maven central is `dev620`:

Could not find org.jetbrains.compose.material:material:1.2.0-alpha01-dev675.
     Searched in the following locations:
       - <https://repo.maven.apache.org/maven2/org/jetbrains/compose/material/material/1.2.0-alpha01-dev675/material-1.2.0-alpha01-dev675.pom>
       - <https://oss.sonatype.org/content/repositories/snapshots/org/jetbrains/compose/material/material/1.2.0-alpha01-dev675/material-1.2.0-alpha01-dev675.pom>
       - <https://s01.oss.sonatype.org/content/repositories/snapshots/org/jetbrains/compose/material/material/1.2.0-alpha01-dev675/material-1.2.0-alpha01-dev675.pom>

[ephemient]

https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/material/mat[…]l/1.2.0-alpha01-dev675/material-1.2.0-alpha01-dev675.pom

[Kirill Grouchnikov]

maven("https://maven.pkg.jetbrains.space/public/p/compose/dev")

[eygraber]

So the builds aren't going to maven central anymore?

[Kirill Grouchnikov]

Not these pre alpha ones, not always

[eygraber]

So sometimes the pre alpha ones go to maven central? Like dev620?

[Kirill Grouchnikov]

Up to the JB people, really

[ephemient]

all the compose-jb examples use https://maven.pkg.jetbrains.space/public/p/compose/dev even for release versions

[eygraber]

I guess that's a strategy. I'll go back to jetbrains.space then 😄