jianguotian opened a new pull request, #10: URL: https://github.com/apache/paimon-full-text/pull/10
## What - Stop deploying Java artifacts to Apache Nexus staging from the GitHub Actions release workflow. - Keep the RC Java workflow building native libraries and verifying the release profile with `mvn clean verify -Prelease -Dgpg.skip=true -DskipTests`. - Add `tools/deploy_java_staging.sh` so a committer/RM can download the RC native artifacts and run the Maven staging deploy locally. ## Why ASF release guidance treats CI-based signing/staging as sensitive. This keeps CI out of the Java staging deploy path while preserving automated native build checks. ## How to use ```bash cd tools RELEASE_VERSION=0.1.0 RC_NUMBER=1 GITHUB_RUN_ID=<release-java-run-id> ./deploy_java_staging.sh ``` The script expects local Maven/GPG setup for `apache.releases.https`, or `NEXUS_STAGE_DEPLOYER_USER` and `NEXUS_STAGE_DEPLOYER_PW` for a temporary Maven settings file. ## Verification - `bash -n tools/deploy_java_staging.sh` - YAML parsed for `.github/workflows/release-java.yml` and `.github/workflows/release.yml` - `python3 tools/validate_asf_yaml.py` - `mvn -q -f java/pom.xml clean verify -Prelease -Dgpg.skip=true -DskipTests` - Dry-run of `tools/deploy_java_staging.sh` with fake native artifacts and `MVN=true` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
