From 2cb9708f1e7e950dde46b12a15cf802e8afc3429 Mon Sep 17 00:00:00 2001 From: Elie Gambache Date: Mon, 10 Aug 2026 17:58:52 +0300 Subject: [PATCH] Raise the Central Portal upload timeout MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The v1.0.1 publish failed with `Failed to stop service 'maven-central-build-service' > timeout` exactly 60s after the bundle upload started — SONATYPE_CONNECT_TIMEOUT_SECONDS defaults to 60 and is used as the OkHttp read timeout on the upload request. The upload had actually reached the Portal, so the deployment stayed alive and the retry was rejected with "Component with coordinate dev.nucleusframework:composewebview-jvm:1.0.1 is currently being published in another deployment". Give the Portal 10 minutes to answer instead. --- .github/workflows/publish-on-maven.yml | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/.github/workflows/publish-on-maven.yml b/.github/workflows/publish-on-maven.yml index ed93b4e..4d0d965 100644 --- a/.github/workflows/publish-on-maven.yml +++ b/.github/workflows/publish-on-maven.yml @@ -97,8 +97,16 @@ jobs: - name: Setup Gradle uses: gradle/actions/setup-gradle@v4 + # SONATYPE_CONNECT_TIMEOUT_SECONDS defaults to 60s, which is the OkHttp + # read timeout on the bundle upload. The Central Portal regularly takes + # longer to answer, and a timed-out upload still leaves a live deployment + # behind — so the retry then fails with "currently being published in + # another deployment" and the release needs manual cleanup. - name: Publish to Maven Central - run: ./gradlew publishAndReleaseToMavenCentral --no-configuration-cache + run: > + ./gradlew publishAndReleaseToMavenCentral + -PSONATYPE_CONNECT_TIMEOUT_SECONDS=600 + --no-configuration-cache env: ORG_GRADLE_PROJECT_mavenCentralUsername: ${{ secrets.MAVENCENTRALUSERNAME }} ORG_GRADLE_PROJECT_mavenCentralPassword: ${{ secrets.MAVENCENTRALPASSWORD }}