This message was deleted.

Kotlin 1.8.20 is not officially released yet. JetBrains will announce when everything is synced to everywhere, as they always do.

Besides that, you define

mavenCentral()

as project repository. But what you need is it as plugin respository in your settings script. The default

gradlePluginPortal()

redirects to JCenter for missing libs which forwards to MavenCentral for missing libs. But as MavenCentral has it, but JCenter returns 404, JCenter probably has some cache that remembered it didn't see the file. So either declare MC as additional plugin repository before GPP, or just wait until the cache refreshes. Especially as you should wait anyway until the release process finished as @ephemient said. 🙂

About 5 hours ago, Dependabot updated Kotlin from 1.8.10 to 1.8.20 in one of my repos but the branch build failed for the same reason.

Yeah, because it is not intelligent. It does not understand that until the blog post is out the release is not finished. It just sees the new version at MavenCentral and creates the PR. It does not even consider from which repository the dependency is pulled obviously.

Thx for clarification. Adding mavenCentral to

setting.gradle.kts

did the trick (at this mid release time).

pluginManagement {
    repositories {
        gradlePluginPortal()
        mavenCentral()
    }
}

I will see how this will play out with the next Kotlin update. If if will be picked to quickly again I will consider setting Renovate stabilitydays option to delay this update.

It is every release that it gets picked up too early and multiple people here or in Kotlin slack complain that it does not properly work.

Renovate fails all my builds as well, but the weird thing is that it's only JCenter that doesn't have this... https://plugins.gradle.org/m2/org/jetbrains/kotlin/kotlin-scripting-jvm/1.8.20/kotlin-scripting-jvm-1.8.20.pom -> 404 https://repo1.maven.org/maven2/org/jetbrains/kotlin/kotlin-scripting-jvm/1.8.20/kotlin-scripting-jvm-1.8.20.pom -> OK I though we established that GPP redirects to JC which pulls from MC.

Yes, but JCenter gives the 404. Again, it probably has some cache and still thinks it is absent as the cache period didn't expire yet.

Ah, of course, caches everywhere 🙂

you can use

--refresh-versions

flag too

For me, it was on GitHub Actions CI, and I think in some of the projects I don't even have Gradle cache.

@Zak Taccardi

--refresh-versions

can't force the upstream remote repository to refresh its caches