bobbai00 opened a new pull request, #4850:
URL: https://github.com/apache/texera/pull/4850
### What changes were proposed in this PR?
ASF policy requires distributed artifacts to carry `LICENSE`, `NOTICE`, and
(while incubating) `DISCLAIMER`. The RC docker-compose tarball produced by
`.github/workflows/create-release-candidate.yml` was missing them.
This PR adds per-bundle files at `bin/single-node/`:
- `bin/single-node/LICENSE` — plain Apache 2.0 text. The bundle ships only
Texera-authored YAML/SQL/Markdown (`docker-compose.yml`, `nginx.conf`,
`litellm-config.yaml`, `.env`, `README.md`, `examples/`, `sql/`), so the root
`LICENSE`'s `THIRD-PARTY DEPENDENCIES` section (which attributes bundled
MIT-licensed source from mbknor-jackson-jsonschema, Angular formly, TypeFox
monaco-languageclient, SVGRepo) does **not** apply here. Including those
attributions would be misleading because none of that code is in the tarball.
- `bin/single-node/NOTICE` — verbatim copy of root `NOTICE` (project-level
ASF attribution; applies to any artifact).
- `bin/single-node/DISCLAIMER` — verbatim copy of root `DISCLAIMER`
(incubator boilerplate; applies to any artifact).
The `Create Docker Compose deployment bundle` step in the RC workflow
already `git archive`s `bin/single-node/` recursively, so the new files are
picked up automatically; the step now `cp`s them into `BUNDLE_DIR` alongside
`docker-compose.yml`.
### Any related issues, documentation, discussions?
Closes #4847.
Note on scope: the issue is specific to the docker-compose tarball. The Helm
chart (`bin/k8s/`) has the same gap but is intentionally left alone here per
the issue scope.
### How was this PR tested?
No automated test — this only takes effect during `Create and upload release
candidate artifacts` (manual `workflow_dispatch`). Verified by inspection:
- The new files are at `bin/single-node/{LICENSE,NOTICE,DISCLAIMER}`;
`LICENSE` is the first 202 lines of root `LICENSE` (Apache 2.0 boilerplate,
ending at "limitations under the License").
- The workflow's `git archive` already pulls `bin/single-node/`, and three
new `cp` lines copy them into the bundle directory before tarballing.
The next RC build will exercise the path end-to-end.
### 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]
