fix: reconcile repository MIT licensing (#132)#145
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR reconciles first-party license declarations across the repository to match the authoritative MIT license (as declared in LICENSE, GitHub metadata, and .lit/repository.yml) and adds a deterministic CI validator to prevent future drift.
Changes:
- Normalize first-party MIT declarations in
package.json,package-lock.json,README.md, andCONTRIBUTING.md. - Add a new first-party repository license consistency validator +
node:testcoverage. - Wire the new validator into the existing
test:licensesgate while keeping the third-party license flow intact.
Reviewed changes
Copilot reviewed 6 out of 7 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| scripts/lib/repository-license.mjs | Implements a deterministic validator that checks key first-party MIT declarations. |
| scripts/lib/repository-license.test.mjs | Adds node:test coverage for consistent and mismatched license declarations. |
| scripts/check-repository-license.mjs | Adds a CLI entrypoint that reads repo files and runs the validator during CI/license checks. |
| package.json | Switches license to MIT and runs the new validator as part of test:licenses. |
| package-lock.json | Updates the lockfile root package license to MIT for consistency. |
| README.md | Updates the License section to declare MIT (matching LICENSE and badges). |
| CONTRIBUTING.md | Updates contributor licensing language to MIT. |
Deploying lightning-it-documentation with
|
| Latest commit: |
d9c8d41
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://448ac812.lightning-it-documentation.pages.dev |
| Branch Preview URL: | https://agent-issue-132-governance-l.lightning-it-documentation.pages.dev |
litroc
enabled auto-merge
July 27, 2026 04:12
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.
Summary
LICENSE, GitHub repository metadata, and managed.lit/repository.ymlRoot cause and impact
The repository license and GitHub metadata were already MIT, but package metadata, the README license paragraph, and contributor guidance still declared Apache-2.0. This change removes that governance ambiguity and makes future mismatches fail CI.
The managed
.lit/repository.ymlremains unchanged and continues to be owned bylightning-it/shared-assets-lit.Evidence
The architecture baseline now records the implementation transition without retaining an active conflicting license value. The approval validator consequently continues to fail closed until issue #2 supplies exact-tree, role-matched approval; this is the independent production-publication gate and is not bypassed by this PR.
Rollback
Revert this PR. No dependency versions, third-party license texts, managed assets, credentials, DNS, or production configuration are changed.
Closes #132