chore: add MIT LICENSE and declare license metadata - #84
Open
innovus-h wants to merge 1 commit into
Open
Conversation
README advertises MIT in two places (the badge and the `[MIT](LICENSE)` link), but no LICENSE file existed and pyproject.toml declared no license, so the repo defaulted to "all rights reserved" and GitHub/PyPI both reported no license. - Add a top-level LICENSE with the standard MIT text, attributed to Inference R&D, Inc. per maintainer guidance in the issue thread. - Declare `license = "MIT"` and `license-files = ["LICENSE"]` in pyproject.toml. hatchling 1.28.0 supports PEP 639, so the built wheel now carries `License-Expression: MIT` / `License-File: LICENSE` (Metadata-Version 2.4) and bundles the LICENSE in dist-info. Fixes context-labs#34
innovus-h
force-pushed
the
add-mit-license
branch
from
July 28, 2026 08:27
66e1704 to
9ae80cc
Compare
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.
Fixes #34.
Problem
README.mdadvertises MIT in two places, but the repo had noLICENSEfile andpyproject.tomldeclared no license — so the code defaulted to "all rights reserved", contradicting the README, and bothGET /repos/context-labs/haloand thehalo-enginePyPI metadata reported no license.README.md:23-24— MIT badgeREADME.md:307—[MIT](LICENSE)link, previously a 404LICENSEin the tree was the vendoreddemo/appworld/LICENSE(Apache-2.0, untouched here)Changes
LICENSE— standard MIT text at the repo root. Attributed toInference R&D, Inc., per @samheutmaker's reply on Repo is missing LICENSE file despite MIT badge in README #34. Copyright year 2026.pyproject.toml— addedlicense = "MIT"andlicense-files = ["LICENSE"].The PEP 639 spelling is used rather than the legacy
license = {text = "MIT"}since the build backend is alreadyhatchling==1.28.0, which supports it.Verification
Built the wheel and inspected the metadata:
The LICENSE is also bundled at
halo_engine-0.2.2.dist-info/licenses/LICENSE, so the next PyPI release will carry correct license metadata. No source files touched.Credit to @yurekami for the original report and diagnosis in #34.
Note
Low Risk
Documentation and packaging metadata only; no runtime or security-sensitive code paths change.
Overview
Adds a root
LICENSEwith standard MIT text (copyright Inference R&D, Inc., 2026) so the README’s MIT badge and[MIT](LICENSE)link match the repo instead of implying “all rights reserved.”Updates
pyproject.tomlwith PEP 639license = "MIT"andlicense-files = ["LICENSE"]so GitHub and PyPI/halo-enginewheel metadata report MIT and bundle the license file—no application or runtime code changes.Reviewed by Cursor Bugbot for commit 9ae80cc. Bugbot is set up for automated code reviews on this repo. Configure here.