This is an automated email from the ASF dual-hosted git repository.
JingsongLi pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/paimon.git
The following commit(s) were added to refs/heads/master by this push:
new e20a7d7295 [release] Refresh release workflow maintenance
e20a7d7295 is described below
commit e20a7d7295d71a9a74eca405d33b97c69771e7c0
Author: JingsongLi <[email protected]>
AuthorDate: Sun Aug 2 10:32:21 2026 +0800
[release] Refresh release workflow maintenance
---
.github/workflows/release-java.yml | 18 ++++++++++++------
.github/workflows/release-python-publish.yml | 2 +-
.github/workflows/release-python.yml | 4 ++--
.github/workflows/release.yml | 2 +-
docs/docs/project/creating-a-release.md | 6 ++++++
docs/docs/project/verifying-a-release-candidate.md | 5 ++++-
paimon-spark/paimon-spark-common/pom.xml | 2 ++
7 files changed, 28 insertions(+), 11 deletions(-)
diff --git a/.github/workflows/release-java.yml
b/.github/workflows/release-java.yml
index 65fbde7166..12160e9808 100644
--- a/.github/workflows/release-java.yml
+++ b/.github/workflows/release-java.yml
@@ -59,7 +59,7 @@ jobs:
cache: maven
- name: Set up Maven
- uses: stCarolas/setup-maven@d6af6abeda15e98926a57b5aa970a96bb37f97d1 #
v5
+ uses: stCarolas/setup-maven@12eb41b233df95d49b0c11fc1b5bc8312e5d4ce0 #
v5.1
with:
maven-version: 3.8.8
@@ -166,9 +166,12 @@ jobs:
capture_expected_projects \
-Papache-release,docs-and-source,flink2 \
-pl
org.apache.paimon:paimon-flink-2.0,org.apache.paimon:paimon-flink-2.1,org.apache.paimon:paimon-flink-2.2,org.apache.paimon:paimon-flink2-common,org.apache.paimon:paimon-iceberg
+ # This install only supplies reactor dependencies for the deploy
+ # below. Their Javadocs are built by the owning release lane.
mvn clean install -ntp -B \
-Pdocs-and-source,flink2 \
- -DskipTests -Dstyle.color=never \
+ -DskipTests -Dmaven.javadoc.skip=true \
+ -Dstyle.color=never \
-pl
org.apache.paimon:paimon-flink-2.0,org.apache.paimon:paimon-flink-2.1,org.apache.paimon:paimon-flink-2.2,org.apache.paimon:paimon-iceberg
\
-am \
2>&1 | tee "${log}"
@@ -184,9 +187,12 @@ jobs:
capture_expected_projects \
-Papache-release,docs-and-source,spark4 \
-pl
org.apache.paimon:paimon-spark-common_2.13,org.apache.paimon:paimon-spark4-common_2.13,org.apache.paimon:paimon-spark-4.0_2.13,org.apache.paimon:paimon-spark-4.1_2.13
+ # This install only supplies reactor dependencies for the deploy
+ # below. Their Javadocs are built by the owning release lane.
mvn clean install -ntp -B \
-Pdocs-and-source,spark4 \
- -DskipTests -Dstyle.color=never \
+ -DskipTests -Dmaven.javadoc.skip=true \
+ -Dstyle.color=never \
-pl
paimon-spark/paimon-spark-4.0,paimon-spark/paimon-spark-4.1 \
-am \
2>&1 | tee "${log}"
@@ -349,7 +355,7 @@ jobs:
} > "release-java/${LANE}-manifest.txt"
- name: Upload Java repository lane
- uses: actions/upload-artifact@v5
+ uses: actions/upload-artifact@v6
with:
name: java-repository-${{ matrix.lane }}
path: release-java/
@@ -361,7 +367,7 @@ jobs:
needs: package
runs-on: ubuntu-latest
steps:
- - uses: actions/download-artifact@v5
+ - uses: actions/download-artifact@v6
with:
pattern: java-repository-*
path: release-java/lanes
@@ -488,7 +494,7 @@ jobs:
} > release-java/final/paimon-maven-repository-manifest.txt
- name: Upload combined Java repository
- uses: actions/upload-artifact@v5
+ uses: actions/upload-artifact@v6
with:
name: java-release-repository
path: release-java/final/
diff --git a/.github/workflows/release-python-publish.yml
b/.github/workflows/release-python-publish.yml
index d2c226d188..9ae869a590 100644
--- a/.github/workflows/release-python-publish.yml
+++ b/.github/workflows/release-python-publish.yml
@@ -48,7 +48,7 @@ jobs:
steps:
- uses: actions/checkout@v6
- - uses: actions/download-artifact@v5
+ - uses: actions/download-artifact@v6
with:
name: pypaimon-distributions
path: dist
diff --git a/.github/workflows/release-python.yml
b/.github/workflows/release-python.yml
index 7c0cafb2e1..0dc5112821 100644
--- a/.github/workflows/release-python.yml
+++ b/.github/workflows/release-python.yml
@@ -48,7 +48,7 @@ jobs:
- uses: actions/checkout@v6
- name: Set up Python
- uses: actions/setup-python@v5
+ uses: actions/setup-python@v6
with:
python-version: "3.11"
cache: pip
@@ -145,7 +145,7 @@ jobs:
PY
- name: Upload PyPaimon distributions
- uses: actions/upload-artifact@v5
+ uses: actions/upload-artifact@v6
with:
name: pypaimon-distributions
path: |
diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index 814d014678..caaf86a89e 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -55,7 +55,7 @@ jobs:
cache: maven
- name: Set up Maven
- uses: stCarolas/setup-maven@d6af6abeda15e98926a57b5aa970a96bb37f97d1 #
v5
+ uses: stCarolas/setup-maven@12eb41b233df95d49b0c11fc1b5bc8312e5d4ce0 #
v5.1
with:
maven-version: 3.8.8
diff --git a/docs/docs/project/creating-a-release.md
b/docs/docs/project/creating-a-release.md
index ed1e157167..b4a6397335 100644
--- a/docs/docs/project/creating-a-release.md
+++ b/docs/docs/project/creating-a-release.md
@@ -187,6 +187,12 @@ RELEASE_CANDIDATE="${RC_NUMBER}" \
This creates the local branch `release-PAIMON_VERSION-rcRC_NUMBER`. Use it only
to prepare the candidate commit; do not push this branch to the remote.
+The remote release branch is not frozen by an RC. It may continue receiving
+fixes for a later RC or maintenance release, and its head does not need to stay
+equal to the published RC tag. If a later branch change must be included in the
+release currently under vote, create a new RC from that updated branch state;
+never move or replace the existing RC tag.
+
Change all Maven modules from `PAIMON_VERSION-SNAPSHOT` to
`PAIMON_VERSION`. The helper commits the Maven version change:
diff --git a/docs/docs/project/verifying-a-release-candidate.md
b/docs/docs/project/verifying-a-release-candidate.md
index 97988b0265..3129a32e1e 100644
--- a/docs/docs/project/verifying-a-release-candidate.md
+++ b/docs/docs/project/verifying-a-release-candidate.md
@@ -98,7 +98,10 @@ git -C paimon-candidate-git rev-parse
"refs/tags/${RC_TAG}^{commit}"
The resolved commit must equal both the SHA in the vote email and the
`head_sha` of the successful Release workflow run. Inspect the commits since
the
-previous release and confirm that the RC tag is attached to the intended
branch.
+previous release and confirm that the RC tag was prepared from the intended
+release branch. The release branch may advance after the RC is tagged and does
+not need to remain equal to the RC commit; verify the immutable tag and
candidate
+artifacts announced for the vote.
## Inspect the source archives
diff --git a/paimon-spark/paimon-spark-common/pom.xml
b/paimon-spark/paimon-spark-common/pom.xml
index 6824237d1d..80ecd1243e 100644
--- a/paimon-spark/paimon-spark-common/pom.xml
+++ b/paimon-spark/paimon-spark-common/pom.xml
@@ -35,6 +35,8 @@ under the License.
<properties>
<spark.version>${paimon-spark-common.spark.version}</spark.version>
+ <!-- Javadoc cannot resolve the generated Spark and Scala shim
classes. -->
+ <maven.javadoc.skip>true</maven.javadoc.skip>
</properties>
<dependencies>
