venkateshwaracholan opened a new pull request, #4581:
URL: https://github.com/apache/polaris/pull/4581

   Fixes #3508
   
   ## Summary
   
   Fix the GitHub Release publishing workflow to include ZIP artifacts when 
attaching release assets.
   
   ## Root Cause
   
   The workflow collects release artifacts using a `find` expression that 
matches:
   
   * `*.tar.gz`
   * `*.tgz`
   * `*.asc`
   * `*.sha512`
   * `*.prov`
   
   but does not match `*.zip`.
   
   As a result, ZIP binary packages are excluded by the selector while their 
corresponding checksum and signature files are still attached.
   
   ## Changes
   
   * Add `*.zip` to the artifact attachment filter.
   * Parenthesize the `find` predicates so the file-type filter is applied 
consistently across all artifact patterns.
   
   ## Validation
   
   Verified the release artifact flow:
   
   * `runtime/distribution/build.gradle.kts` defines a `distZip` distribution 
artifact.
   * `release-3-build-and-publish-artifacts.yml` stages files from 
`runtime/distribution/build/distributions/`.
   * Reproduced the artifact-selection logic locally:
     * The previous selector included `*.zip.asc` and `*.zip.sha512` but 
excluded `*.zip`.
     * The updated selector includes the ZIP artifact together with its 
signature and checksum files.
   
   ## Checklist
   - [ ] ๐Ÿ›ก๏ธ Don't disclose security issues! (contact [email protected])
   - [ ] ๐Ÿ”— Clearly explained why the changes are needed, or linked related 
issues: Fixes #
   - [ ] ๐Ÿงช Added/updated tests with good coverage, or manually tested (and 
explained how)
   - [ ] ๐Ÿ’ก Added comments for complex logic
   - [ ] ๐Ÿงพ Updated `CHANGELOG.md` (if needed)
   - [ ] ๐Ÿ“š Updated documentation in `site/content/in-dev/unreleased` (if needed)
   


-- 
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]

Reply via email to