Repository navigation
Conversation
…e code Each crate declares its license in `package.license`, either `Apache-2.0` or `BUSL-1.1`, with an absent field meaning BSL. The new `crate-licenses` lint fails when a file in an Apache crate carries the BSL header, or when an Apache crate has a BSL normal or build dependency. BSL crates may contain Apache files, since some are derived from Apache-licensed third-party code. The `license` fields now match what the crates contain. The `dyncfg*`, `proto`, and `mz` crates claimed Apache but consist of BSL files or link BSL crates, so they become `BUSL-1.1`. The four crates labeled `proprietary` carry BSL headers and become `BUSL-1.1` too. `mz` gains `publish = false` like every other workspace crate, so cargo-deny skips it. `timely-util`, `sql-lexer`, and `sql-parser` gain an explicit `Apache-2.0`. BSL files that ended up in Apache crates, and two BSL build dependencies, are allowlisted until relabeling them is approved. Stale allowlist entries fail the lint. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Every crate now sets `package.license`, so no crate is BSL by omission. The crates that had no field get `BUSL-1.1`, except `sql-lexer-wasm` and `sql-parser-wasm`, whose files are Apache and which depend only on Apache crates. The lint also fails on a file whose Materialize copyright header names neither license. No file does today. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 9, 2026
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Several crates that are meant to be Apache-licensed contain BSL files, and some crates'
licensefields do not match their contents. Nothing checked this, becausemisc/lint/copyright.pyonly verifies the copyright line.The new
crate-licensescheck inbin/lint-cargomakespackage.licensethe source of truth. Every crate must set it toApache-2.0orBUSL-1.1. The check fails when a file in an Apache crate carries the BSL header, when an Apache crate has a BSL normal or build dependency, or when a file's Materialize copyright header names neither license. BSL crates may contain Apache files, since some are derived from Apache-licensed third-party code.The
licensefields now match the crates' contents.dyncfg*,proto, andmzclaimed Apache but consist of BSL files or link BSL crates, so they becomeBUSL-1.1, as do the fourproprietarycrates.mzgainspublish = falselike every other workspace crate, so cargo-deny skips it. Crates without a field getBUSL-1.1, excepttimely-util,sql-lexer,sql-parser,sql-lexer-wasm, andsql-parser-wasm, which declareApache-2.0.BSL files inside Apache crates (mostly in
timely-util) and the BSL build dependencies ofprofandsql-parserare allowlisted. Relabeling them Apache loosens their license and needs sign-off first. Stale allowlist entries fail the lint, so the list only shrinks.Posted by Claude Code.
🤖 Generated with Claude Code