From 1806dc232395d2a446a2eef17886194b5dd27051 Mon Sep 17 00:00:00 2001
From: Will Jones <willjones127@gmail.com>
Date: Thu, 12 Nov 2026 11:34:14 -0800
Subject: [PATCH] ci(java): publish beta releases to Fury instead of Maven
 Central (#5011)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

## Summary

Java publishing has failed since `v0.42.0-beta.10` because the `lancedb`
Sonatype org hit Maven Central's monthly release-count limit:

```text
Publishing blocked: your organization has reached its monthly release count limit. Grace period ended 2026-11-08. Usage resets 2026-12-01.
```

This sends beta tags to `https://maven.fury.io/lancedb/` instead,
matching how Python publishes betas to `pypi.fury.io/lancedb`. Stable
releases still go to Maven Central.

```text
tag contains "beta" -> setup-java server "fury"  -> mvn deploy -P deploy-to-fury
otherwise           -> setup-java server "ossrh" -> mvn deploy -P deploy-to-ossrh
```

- `java/pom.xml`: new `deploy-to-fury` profile that points
`distributionManagement` at Fury.
- `java/README.md`: explains how to add the Fury and `maven.lance.org`
repositories to use a beta.

Requires a `FURY_TOKEN` secret with push access to the `lancedb` Fury
account. The token is passed as the Maven username with a placeholder
password. That follows Gemfury's convention but hasn't been tested
against Fury yet.

## Evidence

Running the beta path locally (`deploy -pl lancedb-core -am -P
deploy-to-fury`) against a file repository deployed `lancedb-parent`
(POM) and `lancedb-core` (JAR, POM, sources, javadoc).
`help:effective-pom -P deploy-to-fury` resolves the release repository
to `https://maven.fury.io/lancedb/`.

## Merge Risk

**Door:** Two-way. This only changes where future betas are published;
reverting the workflow restores Central publishing.
**Blast Radius:** `release-ci`. Beta consumers need the extra
repository; stable consumers are unaffected.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
---
 .github/workflows/java-publish.yml | 20 +++++++++++++-----
 java/README.md                     | 34 ++++++++++++++++++++++++++++++
 java/pom.xml                       |  9 ++++++++
 3 files changed, 58 insertions(+), 5 deletions(-)

diff --git a/.github/workflows/java-publish.yml b/.github/workflows/java-publish.yml
index 094aa552a..35d052de9 100644
--- a/.github/workflows/java-publish.yml
+++ b/.github/workflows/java-publish.yml
@@ -39,9 +39,11 @@ jobs:
           distribution: temurin
           java-version: 8
           cache: "maven"
-          server-id: ossrh
-          server-username: SONATYPE_USER
-          server-password: SONATYPE_TOKEN
+          # Betas go to Fury and stable releases to Maven Central, which limits
+          # how many releases an organization may publish each month.
+          server-id: ${{ contains(github.ref, 'beta') && 'fury' || 'ossrh' }}
+          server-username: ${{ contains(github.ref, 'beta') && 'FURY_TOKEN' || 'SONATYPE_USER' }}
+          server-password: ${{ contains(github.ref, 'beta') && 'FURY_PASSWORD' || 'SONATYPE_TOKEN' }}
           gpg-private-key: ${{ secrets.GPG_PRIVATE_KEY }}
           gpg-passphrase: MAVEN_GPG_PASSPHRASE
       - name: Set git config
@@ -52,8 +54,16 @@ jobs:
         if: github.event_name == 'pull_request'
         run: |
           ./mvnw --batch-mode -DskipTests package -pl lancedb-core -am
-      - name: Publish
-        if: startsWith(github.ref, 'refs/tags/v')
+      - name: Publish to Fury
+        if: startsWith(github.ref, 'refs/tags/v') && contains(github.ref, 'beta')
+        run: |
+          ./mvnw --batch-mode -DskipTests deploy -pl lancedb-core -am -P deploy-to-fury
+        env:
+          FURY_TOKEN: ${{ secrets.FURY_TOKEN }}
+          # Fury authenticates with the token as the username; the password is ignored.
+          FURY_PASSWORD: NOPASS
+      - name: Publish to Maven Central
+        if: startsWith(github.ref, 'refs/tags/v') && !contains(github.ref, 'beta')
         run: |
           echo "use-agent" >> ~/.gnupg/gpg.conf
           echo "pinentry-mode loopback" >> ~/.gnupg/gpg.conf
diff --git a/java/README.md b/java/README.md
index fd163b9f1..85e7e85ba 100644
--- a/java/README.md
+++ b/java/README.md
@@ -1,5 +1,39 @@
 # LanceDB Java Enterprise Client
 
+## Installation
+
+Stable releases of `com.lancedb:lancedb-core` are published to Maven Central.
+
+Beta releases are published to `https://maven.fury.io/lancedb/` instead. They
+depend on Lance beta releases, which are published to `https://maven.lance.org`.
+To use a beta, add both repositories alongside Maven Central:
+
+```xml
+<repositories>
+    <repository>
+        <id>lancedb</id>
+        <url>https://maven.fury.io/lancedb/</url>
+    </repository>
+    <repository>
+        <id>lance</id>
+        <url>https://maven.lance.org</url>
+    </repository>
+</repositories>
+```
+
+For Gradle:
+
+```kotlin
+repositories {
+    mavenCentral()
+    maven { url = uri("https://maven.fury.io/lancedb/") }
+    maven { url = uri("https://maven.lance.org") }
+}
+```
+
+Use an explicit version, including the full `-beta.N` suffix. Beta versions are
+Maven releases, not `SNAPSHOT` versions.
+
 ## Configuration and Initialization
 
 ### LanceDB Cloud (legacy)
diff --git a/java/pom.xml b/java/pom.xml
index df709fb4f..fc89ebe4c 100644
--- a/java/pom.xml
+++ b/java/pom.xml
@@ -318,6 +318,15 @@
                 </plugins>
             </build>
         </profile>
+        <profile>
+            <id>deploy-to-fury</id>
+            <distributionManagement>
+                <repository>
+                    <id>fury</id>
+                    <url>https://maven.fury.io/lancedb/</url>
+                </repository>
+            </distributionManagement>
+        </profile>
         <profile>
             <id>deploy-to-ossrh</id>
             <build>