Skip to content

Relicense to Apache-2.0 - #2

Merged
eliahilse merged 1 commit into
mainfrom
relicense
Aug 7, 2026
Merged

Relicense to Apache-2.0#2
eliahilse merged 1 commit into
mainfrom
relicense

Conversation

@eliahilse

Copy link
Copy Markdown
Owner

The relicense commit missed the #1 merge window — this is that same commit, rebased onto main.

  • LICENSE — canonical Apache 2.0 text from apache.org, appendix filled in with Copyright 2025-2026 Elia Hilse (2025 is the repo's first commit year, so the range covers what was already published under the old terms)
  • NOTICE — at the root, and copied into packages/lb with "files": ["dist", "LICENSE", "NOTICE"] so it ships in the npm tarball; npm includes LICENSE on its own but not NOTICE, which Apache-2.0 §4(d) requires downstream distributions to carry
  • license fields on the root and @hyperfly/lb, both READMEs, and an apache-2.0 link in the site footer

Also ignores the generated .open-next output in eslint — it started tripping --max-warnings 0 once a deploy build existed in the working tree.

This only changes terms going forward; hyperfly@0.1.0 on npm stays Elastic-2.0 for anyone who already took a copy.

🤖 Generated with Claude Code

https://claude.ai/code/session_01RULgztJ9WBtad1KRyJG4eq

Copyright 2025-2026 Elia Hilse. LICENSE is the canonical Apache text from
apache.org with the appendix filled in; NOTICE ships alongside it and is
included in the lb package's published files, since Apache-2.0 requires
downstream distributions to carry it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RULgztJ9WBtad1KRyJG4eq
@eliahilse
eliahilse merged commit bf6f467 into main Aug 7, 2026
@eliahilse eliahilse mentioned this pull request Aug 7, 2026
eliahilse added a commit that referenced this pull request Aug 7, 2026
Stacked on #2 (the relicense branch) because both touch
`packages/lb/package.json` — GitHub retargets this to `main`
automatically once #2 merges.

Runs on every PR and on pushes to main:

```
bun install --frozen-lockfile
bun run lint          # turbo run lint
bun run check-types   # turbo run check-types
```

Driving the root turbo tasks rather than naming apps means a new package
is covered as soon as it declares the scripts. `packages/lb` gains a
`check-types` script for that reason — its `build` script emits
declarations, which CI doesn't need.

Verified locally from a clean tree (no `.next`, no `.open-next`): frozen
install is in sync, both tasks pass, and `next typegen` works without a
prior build.

Concurrency group cancels superseded runs on the same ref.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

https://claude.ai/code/session_01RULgztJ9WBtad1KRyJG4eq

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant