From c6cbcfc99b3930c19cc88290535f15d4218fe90c Mon Sep 17 00:00:00 2001 From: Zhoujie628 Date: Fri, 4 Sep 2026 23:01:29 +0800 Subject: [PATCH 1/2] chore: publish under the net.openan.workflow.sdk coordinates Switch the Maven groupId to net.openan.workflow.sdk so releases can use the Central Portal namespace already owned by the account that publishes the a2a-t-sdk artifacts (same user token). Java package names stay dev.openan.workflow.engine; migrating the coordinates to dev.openan remains a later change once the openan.dev domain is verified. Signed-off-by: Zhoujie628 --- .github/workflows/release.yml | 7 ++++--- README.md | 4 ++-- docs/en/DEVELOPER_GUIDE.md | 2 +- docs/en/INTEGRATION_GUIDE.md | 2 +- docs/zh/DEVELOPER_GUIDE.md | 2 +- docs/zh/INTEGRATION_GUIDE.md | 2 +- pom.xml | 2 +- samples/pom.xml | 6 +++--- spring-boot-starter/pom.xml | 4 ++-- workflow-engine/pom.xml | 2 +- 10 files changed, 17 insertions(+), 16 deletions(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index cf0c8fff..c3b27e5d 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -9,9 +9,10 @@ name: Release to Maven Central # One-time setup (required before the first release can succeed): # 1. Central Portal account: https://central.sonatype.com (register, then generate a # User Token under Account settings — this is the MAVEN_CENTRAL_USERNAME/PASSWORD pair). -# 2. Namespace `dev.openan`: claim it in the Portal once the openan.dev domain is -# available, by adding the TXT record the Portal specifies to the domain's DNS. -# Until the namespace is verified, the Portal rejects every dev.openan upload. +# 2. Namespace `net.openan`: already owned by the Central Portal account that +# publishes the a2a-t-sdk artifacts (same user token), so no extra namespace +# claim is needed. Migrating to `dev.openan` is a future change once the +# openan.dev domain is verified. # 3. GPG signing key: generate one (RSA 4096, no expiry or far expiry), publish the # public key to a keyserver (e.g. https://keyserver.ubuntu.com). The Portal # validates artifact signatures against keyservers. diff --git a/README.md b/README.md index 732e8392..b027a77c 100644 --- a/README.md +++ b/README.md @@ -47,7 +47,7 @@ upgrade guidance. ```xml - dev.openan.workflow.sdk + net.openan.workflow.sdk workflow-engine 1.0.0 @@ -57,7 +57,7 @@ For Spring Boot server-side integration: ```xml - dev.openan.workflow.sdk + net.openan.workflow.sdk spring-boot-starter 1.0.0 diff --git a/docs/en/DEVELOPER_GUIDE.md b/docs/en/DEVELOPER_GUIDE.md index 65f0ce32..3e4f64a6 100644 --- a/docs/en/DEVELOPER_GUIDE.md +++ b/docs/en/DEVELOPER_GUIDE.md @@ -9,7 +9,7 @@ Add to your `pom.xml`: ```xml - dev.openan.workflow.sdk + net.openan.workflow.sdk workflow-engine 1.0.0 diff --git a/docs/en/INTEGRATION_GUIDE.md b/docs/en/INTEGRATION_GUIDE.md index 58fea3cb..4c0897d9 100644 --- a/docs/en/INTEGRATION_GUIDE.md +++ b/docs/en/INTEGRATION_GUIDE.md @@ -20,7 +20,7 @@ callbacks own A2A-T generation, semantic validation, schemas and any LLM calls. ```xml - dev.openan.workflow.sdk + net.openan.workflow.sdk workflow-engine 1.0.0 diff --git a/docs/zh/DEVELOPER_GUIDE.md b/docs/zh/DEVELOPER_GUIDE.md index 8e9bc938..5fae1706 100644 --- a/docs/zh/DEVELOPER_GUIDE.md +++ b/docs/zh/DEVELOPER_GUIDE.md @@ -8,7 +8,7 @@ ```xml - dev.openan.workflow.sdk + net.openan.workflow.sdk workflow-engine 1.0.0 diff --git a/docs/zh/INTEGRATION_GUIDE.md b/docs/zh/INTEGRATION_GUIDE.md index c0eceb10..aa86151d 100644 --- a/docs/zh/INTEGRATION_GUIDE.md +++ b/docs/zh/INTEGRATION_GUIDE.md @@ -18,7 +18,7 @@ A2A-T 工作流执行引擎是一个 Java SDK，用于基于 A2A 协议和 A2A-T ```xml - dev.openan.workflow.sdk + net.openan.workflow.sdk workflow-engine 1.0.0 diff --git a/pom.xml b/pom.xml index da7628ad..482b49e6 100644 --- a/pom.xml +++ b/pom.xml @@ -5,7 +5,7 @@ https://maven.apache.org/xsd/maven-4.0.0.xsd"> 4.0.0 - dev.openan.workflow.sdk + net.openan.workflow.sdk workflow-engine-parent ${revision} pom diff --git a/samples/pom.xml b/samples/pom.xml index b52b81e4..36765e17 100644 --- a/samples/pom.xml +++ b/samples/pom.xml @@ -6,7 +6,7 @@ 4.0.0 - dev.openan.workflow.sdk + net.openan.workflow.sdk workflow-engine-parent ${revision} ../pom.xml @@ -21,7 +21,7 @@ - dev.openan.workflow.sdk + net.openan.workflow.sdk workflow-engine ${revision} @@ -51,7 +51,7 @@ - dev.openan.workflow.sdk + net.openan.workflow.sdk spring-boot-starter ${revision} diff --git a/spring-boot-starter/pom.xml b/spring-boot-starter/pom.xml index 70c94872..4340889c 100644 --- a/spring-boot-starter/pom.xml +++ b/spring-boot-starter/pom.xml @@ -6,7 +6,7 @@ 4.0.0 - dev.openan.workflow.sdk + net.openan.workflow.sdk workflow-engine-parent ${revision} ../pom.xml @@ -24,7 +24,7 @@ - dev.openan.workflow.sdk + net.openan.workflow.sdk workflow-engine ${revision} diff --git a/workflow-engine/pom.xml b/workflow-engine/pom.xml index 258878bc..2c0bb4eb 100644 --- a/workflow-engine/pom.xml +++ b/workflow-engine/pom.xml @@ -6,7 +6,7 @@ 4.0.0 - dev.openan.workflow.sdk + net.openan.workflow.sdk workflow-engine-parent ${revision} ../pom.xml From f7d24a3684f6bdc227bafa66e9b562dcee894f7d Mon Sep 17 00:00:00 2001 From: Zhoujie628 Date: Fri, 4 Sep 2026 23:12:38 +0800 Subject: [PATCH 2/2] fix(ci): deploy the parent pom so Central can resolve coordinates The first v0.0.1 deployment was rejected because the module poms take their groupId from the parent and the release command deployed only workflow-engine and spring-boot-starter, leaving the bundle without a resolvable parent. Deploy the full reactor instead; samples stays excluded via maven.deploy.skip. Signed-off-by: Zhoujie628 --- .github/workflows/release.yml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index c3b27e5d..6b919ea6 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -23,10 +23,11 @@ name: Release to Maven Central # SIGNING_KEY_ID key id (last 8 hex chars is enough) # SIGNING_PASSWORD private key passphrase # -# Publishing scope: only workflow-engine and spring-boot-starter are deployed. -# samples is excluded from deployment via maven.deploy.skip, but the release gate still -# builds and tests the full main reactor (main has no vendor-jar dependency; the Eastcom -# adapter exists only on the dev branch). +# Publishing scope: the parent pom, workflow-engine and spring-boot-starter are deployed. +# The parent must ship: module poms take their groupId from it, and Central rejects a +# bundle whose module coordinates cannot be resolved. samples is excluded from deployment +# via maven.deploy.skip, but the release gate still builds and tests the full main reactor +# (main has no vendor-jar dependency; the Eastcom adapter exists only on the dev branch). on: push: @@ -134,7 +135,6 @@ jobs: VERSION="${GITHUB_REF_NAME#v}" echo "Publishing version ${VERSION} from tag ${GITHUB_REF_NAME}" mvn -B -Prelease deploy \ - -pl workflow-engine,spring-boot-starter \ -Drevision="${VERSION}" \ -Dgpg.executable=gpg \ -Dgpg.keyname="${SIGNING_KEY_ID}"