jianguotian opened a new pull request, #15: URL: https://github.com/apache/paimon-full-text/pull/15
## What changed - bundle a generated third-party license report in Java and Python binary distributions, including component/version details, license texts, and copyright notices - keep Java and Python reports target-aware so each binary distribution documents the Rust components it can contain - upgrade `crossbeam-epoch` from 0.9.18 to 0.9.20 and run `cargo deny --locked check advisories` in CI - regenerate and diff the checked-in Rust dependency and license metadata in CI - smoke-test the final wheels and assembled JAR on the release platform matrix (Linux x86_64/aarch64, macOS arm64, and Windows x86_64 as applicable) ## Release impact This addresses the RC3 binary-distribution blockers: 1. The JAR and wheels statically include Rust dependencies, but previously shipped only an SPDX dependency list rather than the applicable third-party license texts and notices. 2. RC3 locked `crossbeam-epoch` 0.9.18, which is affected by `RUSTSEC-2026-0204`; 0.9.20 contains the fix. 3. CI checked license policy but did not scan RustSec advisories. 4. Most release-platform artifacts were built but not exercised after final packaging. The source distribution's Apache license metadata remains unchanged. The additional license appendix and generated report are added only to binary packages. ## Validation - `cargo fmt --all -- --check` - `cargo clippy --all-targets --workspace --locked -- -D warnings` - `cargo test --workspace --locked` (current toolchain and Rust 1.90 MSRV) - `cargo deny --locked check advisories licenses` - regenerated both `cargo-about` reports with `--frozen --fail` and verified no diff - Maven `clean test` and release `package`/`verify` - Python tests and an installed Linux aarch64 wheel smoke test - assembled-JAR smoke test with the Linux aarch64 JNI library - workflow YAML parsing and `actionlint` -- 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]
