Add Apache-2.0 license (Agent Workforce Incorporated) - #526
Conversation
Match Relay's licensing: add the Apache License 2.0 text with a "Copyright 2026 Agent Workforce Incorporated" notice, switch the Rust workspace license from MIT to Apache-2.0, declare Apache-2.0 on the published npm packages, and document it in the README. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018wSz2b9yuVMrhQuEEuMomG
|
Warning Review limit reached
Next review available in: 59 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (29)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
npm and cargo only include a LICENSE that sits in the package directory, so the root file alone left published tarballs without the license text. Copy it into the three npm packages, the eight platform packages, and the two crates.io crates. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018wSz2b9yuVMrhQuEEuMomG
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 10030d7a09
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| ## License | ||
|
|
||
| Apache-2.0 - Copyright 2026 Agent Workforce Incorporated |
There was a problem hiding this comment.
Clarify the macOS app's retained MIT license
This repository-wide Apache-2.0 declaration conflicts with the still-shipped apps/macos/LICENSE, apps/macos/README.md:164-166, and apps/macos/App/Info.plist:27-28, which explicitly identify that subtree and app as MIT-licensed under a different copyright holder. Users cannot tell whether the macOS app was meant to be relicensed or remains an exception; update those declarations with the holder's authorization or state the mixed-license exception here.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
1 issue found and verified against the latest diff
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="LICENSE">
<violation number="1" location="LICENSE:178">
P2: The repository still presents the macOS app under MIT, leaving Burn's distributable surfaces with inconsistent licensing signals. If this relicense is intended to cover the macOS app as well, update `apps/macos/LICENSE` and its attribution in the same change.</violation>
</file>
Tip: cubic can generate docs of your entire codebase and keep them up to date. Try it here.
Re-trigger cubic
|
|
||
| END OF TERMS AND CONDITIONS | ||
|
|
||
| Copyright 2026 Agent Workforce Incorporated |
There was a problem hiding this comment.
P2: The repository still presents the macOS app under MIT, leaving Burn's distributable surfaces with inconsistent licensing signals. If this relicense is intended to cover the macOS app as well, update apps/macos/LICENSE and its attribution in the same change.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At LICENSE, line 178:
<comment>The repository still presents the macOS app under MIT, leaving Burn's distributable surfaces with inconsistent licensing signals. If this relicense is intended to cover the macOS app as well, update `apps/macos/LICENSE` and its attribution in the same change.</comment>
<file context>
@@ -0,0 +1,190 @@
+
+ END OF TERMS AND CONDITIONS
+
+ Copyright 2026 Agent Workforce Incorporated
+
+ Licensed under the Apache License, Version 2.0 (the "License");
</file context>
|
Review status — CI is green (11/11), and the bot findings split into one stale group and one open question. Stale (already fixed in The Open, and a maintainer call rather than something I'll change unilaterally: Generated by Claude Code |
Supersedes #496, which added MIT with an individual copyright. Burn should match Relay's licensing: Apache-2.0, Copyright 2026 Agent Workforce Incorporated.
Changes
LICENSE— Apache License 2.0 text (byte-identical to Relay's) withCopyright 2026 Agent Workforce Incorporated, at the repo root and copied into every published artifact:packages/relayburn,packages/sdk-node,packages/mcp, the 8@relayburn/cli-*/@relayburn/sdk-*platform packages, and the two crates.io crates (relayburn-sdk,relayburn-cli).Cargo.toml— workspacelicensechanged fromMITtoApache-2.0, inherited byrelayburn-sdk,relayburn-cli, andrelayburn-sdk-node.package.json—"license": "Apache-2.0"on the root manifest and every published package. None declared a license before.README.md— License section matching Relay's wording.CHANGELOG.md—[Unreleased]entry.Notes
LICENSEthat sits in the package directory, so the root file alone would have left published tarballs without the license text — hence the per-package copies. Thefilesallowlists did not need editing: npm always includesLICENSEregardless.Verification
cargo metadata --no-depsresolves clean with the new workspace license; all 12 modifiedpackage.jsonfiles parse.npm pack --dry-runinpackages/mcplistsLICENSEin the tarball contents, confirming the allowlist doesn't drop it.🤖 Generated with Claude Code
https://claude.ai/code/session_018wSz2b9yuVMrhQuEEuMomG