Skip to content

chore: relicense under a single MIT license - #36

Merged
DevVig merged 1 commit into
mainfrom
chore/mit-license
Jul 18, 2026
Merged

DevVig merged 1 commit into
mainfrom
chore/mit-license

Conversation

@DevVig

@DevVig DevVig commented Jul 18, 2026

Copy link
Copy Markdown
Owner

Summary

The repo was dual-licensed MIT OR Apache-2.0 (two license files), but GitHub's auto-detector picks one file and was showing the project as "Apache License 2.0" only in the sidebar — hiding the MIT option and misrepresenting the license.

Standardize on MIT (permissive, OSI-approved) so GitHub shows a clean "MIT License" badge and the license is unambiguous.

Changes

  • Rename LICENSE-MITLICENSE; remove LICENSE-APACHE
  • Cargo.toml workspace license = "MIT" (all 5 crates inherit)
  • Homebrew Formula/microbridge.rb: license "MIT"
  • README.md + CONTRIBUTING.md: single MIT, inbound = outbound
  • release.yml: ship LICENSE in archives (not the two old files)
  • .gitignore: exclude stray local artifacts (.playwright-mcp/, settings-keys-twin.png)

Verification

  • cargo metadata reports MIT for all crates
  • No remaining LICENSE-MIT / LICENSE-APACHE / Apache references in project files
  • After merge: confirm GitHub sidebar shows "MIT License"

The repo was dual-licensed MIT OR Apache-2.0 (two files), but GitHub's
auto-detector picks one file and was displaying the project as
"Apache License 2.0" only — hiding the MIT option and misrepresenting the
license in the sidebar.

Standardize on MIT (permissive, OSI-approved) so GitHub shows a clean
"MIT License" badge and the license is unambiguous:

- Rename LICENSE-MIT -> LICENSE; remove LICENSE-APACHE
- Cargo.toml workspace license = "MIT" (all crates inherit)
- Homebrew formula: license "MIT"
- README + CONTRIBUTING: single MIT, inbound = outbound
- release.yml: ship LICENSE (not LICENSE-MIT/LICENSE-APACHE)

Also gitignore stray local artifacts (.playwright-mcp/, settings-keys-twin.png).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings July 18, 2026 13:03
@coderabbitai

coderabbitai Bot commented Jul 18, 2026

Copy link
Copy Markdown

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 49 seconds

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: f5b3dd13-5e85-49c1-8e92-bd35558e6211

📥 Commits

Reviewing files that changed from the base of the PR and between 55a5456 and b5c2141.

📒 Files selected for processing (8)
  • .github/workflows/release.yml
  • .gitignore
  • CONTRIBUTING.md
  • Cargo.toml
  • Formula/microbridge.rb
  • LICENSE
  • LICENSE-APACHE
  • README.md

Comment @coderabbitai help to get the list of available commands.

@DevVig
DevVig merged commit b651cc4 into main Jul 18, 2026
7 checks passed
@DevVig
DevVig deleted the chore/mit-license branch July 18, 2026 13:05

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR standardizes the repository’s licensing to a single MIT license so GitHub’s license detection and downstream packaging metadata consistently report “MIT”.

Changes:

  • Replaces the dual-license setup by removing LICENSE-APACHE and introducing a single root LICENSE (MIT), and updates docs to link to it.
  • Updates Rust workspace and Homebrew formula metadata to MIT.
  • Updates the release workflow packaging step to ship the new LICENSE, and expands .gitignore for local artifacts.

Reviewed changes

Copilot reviewed 6 out of 8 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
README.md Updates the license section to reference the single MIT LICENSE.
LICENSE-APACHE Removes the Apache 2.0 license file as part of standardizing on MIT.
LICENSE Adds the MIT license text as the single license file at repo root.
Formula/microbridge.rb Updates Homebrew formula license metadata to MIT.
CONTRIBUTING.md Updates contribution licensing language to MIT-only (inbound = outbound).
Cargo.toml Updates workspace package license field to MIT.
.gitignore Ignores additional local tooling/debug artifacts.
.github/workflows/release.yml Updates release archives to include LICENSE instead of the prior two license files.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread Cargo.toml
Comment on lines 11 to 15
[workspace.package]
version = "0.1.0"
edition = "2021"
license = "MIT OR Apache-2.0"
license = "MIT"
repository = "https://github.com/DevVig/microbridge"
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.

2 participants