Repository navigation
chore: adopt Apache 2.0 and prepare 0.216.0 - #821
Merged
Merged
Conversation
leemour
force-pushed
the
chore/apache-2.0
branch
from
October 10, 2026 14:32
fb4e1d4 to
3242e87
Compare
leemour
changed the title
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
1 participant
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.
Switch project licensing from MIT to Apache License 2.0, retain copyright attribution, and update package metadata and the README. Include LICENSE in the ONNX and SQLite wrapper tarballs and prepare their 1.0.1 releases while preserving third-party notices.
Prepare cli-messaging 0.216.0. Main already contains the archive-discovery feature from #803; retain its Added changelog entry and use a minor version for the combined release.
Validation: lint, typecheck, coverage (242 files, 2820 tests passed, 2 skipped) and docs checks passed locally after rebasing onto current main. License text, JSON metadata and whitespace were checked. This PR does not alter runtime code or dependency pins. No live messenger operations ran.