Re: [PR] Move Java staging deployment to a hardened local release flow [paimon-mosaic]

["jianguotian (via GitHub)" <gi...@apache.org>]

jianguotian commented on PR #71:
URL: https://github.com/apache/paimon-mosaic/pull/71#issuecomment-5002811399

   Implemented the release-safety fixes in `0091ca3`:
   
   - fail closed on missing option values (including the `--dry-run` regression)
   - reject ignored package inputs
   - bind the workflow run ref/SHA to the exact RC tag and version/RC tuple
   - support Bash 3.2 and normalize Maven settings paths
   - validate the exact JARs in the same Maven lifecycle that deploys them
   - update the release guide and add Ubuntu/macOS regression coverage
   - fix the current Clippy failure
   
   Local validation passed (7 shell regressions on Bash 4.4 and Bash 3.2, JDK 8 Maven artifact validation, Rust fmt/Clippy, workflow YAML/HTML parsing, and `git diff --check`).
   
   The new CI run is waiting for an upstream maintainer to approve the fork workflow: https://github.com/apache/paimon-mosaic/actions/runs/29577101080
   


-- 
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: issues-unsubscribe@paimon.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org