bobbai00 opened a new pull request, #4857:
URL: https://github.com/apache/texera/pull/4857
### What changes were proposed in this PR?
Add a \`build\` job at the top of \`create-release-candidate.yml\` that
calls the reusable \`build.yml\` with:
- \`checkout_ref: \${{ github.event.inputs.tag }}\` — build the tagged
commit (\`build.yml\` already accepts this input).
- \`mode: release\` — strict license-binary check, no
\`--ignore-transitive-version\` (the third mode added in #4734 alongside \`PR\`
and \`nightly\`).
\`create-rc\` now depends on \`build\` via \`needs: build\`. If the tag
doesn't compile or has license-binary drift, no RC tarball is produced and
nothing is signed/uploaded to ASF SVN.
Net diff: +10 lines, no other behavioral change.
### Any related issues, documentation, discussions?
Closes #4856.
Why this matters: today the RC workflow only packages source/docker-compose
tarballs from a tag — it doesn't compile the tagged commit. Strict
license-binary checks only run in the nightly cron. So drift caught only by the
nightly can land in an RC tagged before the next nightly fires. Wiring the
strict-mode build directly into RC creation closes that window.
### How was this PR tested?
- \`python3 -c \"import yaml;
yaml.safe_load(open('.github/workflows/create-release-candidate.yml'))\"\`
parses cleanly.
- Reviewed by inspection: \`build.yml\` accepts \`checkout_ref\` (default
\`\"\"\` → falls through to \`github.sha\`) and \`mode\` (default \`PR\`).
Passing \`mode: release\` flips off \`--ignore-transitive-version\` in all 5
license-check invocations inside \`build.yml\`.
End-to-end exercise: the next \`workflow_dispatch\` of \`Create and upload
release candidate artifacts\` will run this gated path. Quick fork test
possible via \`gh workflow run\` with a local tag.
### Was this PR authored or co-authored using generative AI tooling?
Generated-by: Claude Code (claude-opus-4-7)
--
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]
