Skip to content

fix(release): ship LICENSE/NOTICE/DISCLAIMER in docker-compose tarball#4850

Merged
bobbai00 merged 2 commits into
apache:mainfrom
bobbai00:fix/4847-include-license-notice-disclaimer-compose-tarball
May 3, 2026
Merged

fix(release): ship LICENSE/NOTICE/DISCLAIMER in docker-compose tarball#4850
bobbai00 merged 2 commits into
apache:mainfrom
bobbai00:fix/4847-include-license-notice-disclaimer-compose-tarball

Conversation

@bobbai00
Copy link
Copy Markdown
Contributor

@bobbai00 bobbai00 commented May 3, 2026

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 — copy of root NOTICE (project-level ASF attribution; applies to any artifact).
  • bin/single-node/DISCLAIMER — copy of root DISCLAIMER

Any related issues, documentation, discussions?

Closes #4847.

How was this PR tested?

Was this PR authored or co-authored using generative AI tooling?

Generated-by: Claude Code (claude-opus-4-7)

ASF policy requires distributed artifacts to carry LICENSE, NOTICE, and
(while incubating) DISCLAIMER. The RC docker-compose tarball produced by
create-release-candidate.yml was missing them.

Add per-bundle files at bin/single-node/. The bundle ships only Texera-
authored YAML/SQL/Markdown, so its LICENSE is plain Apache 2.0 (the root
LICENSE's THIRD-PARTY DEPENDENCIES section covers code that isn't shipped
in this artifact). NOTICE and DISCLAIMER are the project-level files,
identical to root.

Closes apache#4847

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@github-actions github-actions Bot added fix ci changes related to CI dev labels May 3, 2026
@codecov-commenter
Copy link
Copy Markdown

codecov-commenter commented May 3, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 43.41%. Comparing base (7dc68ba) to head (9271622).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main    #4850      +/-   ##
============================================
+ Coverage     43.37%   43.41%   +0.03%     
- Complexity     2040     2111      +71     
============================================
  Files           957      957              
  Lines         34077    34946     +869     
  Branches       3753     3893     +140     
============================================
+ Hits          14782    15171     +389     
- Misses        18506    18971     +465     
- Partials        789      804      +15     
Flag Coverage Δ
access-control-service 28.12% <ø> (ø)
agent-service 33.49% <ø> (-0.24%) ⬇️
amber 41.98% <ø> (+0.37%) ⬆️
computing-unit-managing-service 0.00% <ø> (ø)
config-service 0.00% <ø> (ø)
file-service 32.40% <ø> (-0.85%) ⬇️
frontend 34.97% <ø> (-0.31%) ⬇️
python 85.21% <ø> (-0.14%) ⬇️
workflow-compiling-service 47.72% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@bobbai00 bobbai00 requested review from aglinxinyuan May 3, 2026 08:43
@bobbai00 bobbai00 added release/v1.1.0-incubating back porting to release/v1.1.0-incubating labels May 3, 2026
@aglinxinyuan aglinxinyuan added the emergency Pull requests that need to be merged ASAP label May 3, 2026
@bobbai00 bobbai00 enabled auto-merge (squash) May 3, 2026 09:21
@bobbai00 bobbai00 merged commit 3d80393 into apache:main May 3, 2026
37 checks passed
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 3, 2026

Backport to release/v1.1.0-incubating succeeded as 7f2496a. Run

Yicong-Huang pushed a commit that referenced this pull request May 3, 2026
#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` — copy of root `NOTICE` (project-level ASF
attribution; applies to any artifact).
- `bin/single-node/DISCLAIMER` — copy of root `DISCLAIMER`

### Any related issues, documentation, discussions?

Closes #4847.

### How was this PR tested?

### Was this PR authored or co-authored using generative AI tooling?

Generated-by: Claude Code (claude-opus-4-7)

(backported from commit 3d80393)

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci changes related to CI dev emergency Pull requests that need to be merged ASAP fix release/v1.1.0-incubating back porting to release/v1.1.0-incubating

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Include LICENSE, NOTICE and DISCLAIMER in docker compose tarball

3 participants