Skip to content

Relicense: GPL-2.0-only → GPL-3.0-or-later#818

Merged
tomcasaburi merged 2 commits into
masterfrom
chore/relicense-gpl-3.0-or-later
Jun 9, 2026
Merged

Relicense: GPL-2.0-only → GPL-3.0-or-later#818
tomcasaburi merged 2 commits into
masterfrom
chore/relicense-gpl-3.0-or-later

Conversation

@tomcasaburi

@tomcasaburi tomcasaburi commented Jun 2, 2026

Copy link
Copy Markdown
Member

Why

seedit is currently GPL-2.0-only but depends on @bitsocial/bitsocial-react-hooks (GPL-3.0-or-later@pkcprotocol/pkc-js). GPL-2.0-only is legally incompatible with GPL-3.0-or-later — there is no common license version the combined work can be distributed under. This is a live conflict, not just staleness.

Moving to GPL-3.0-or-later resolves it and aligns seedit with the rest of the core stack.

Changes

  • package.json: licenseGPL-3.0-or-later
  • LICENSE: replace verbatim GPLv2 text with GPLv3
  • README.md: license badge label

Notes

  • Relicensing authorized by cofounder / copyright holder.
  • README still contains stale bitsocialhq org links (wrong org) — intentionally out of scope here; tracked separately.
  • Licensing strategy, not formal legal advice.

Note

Low Risk
Documentation and SPDX metadata only; no runtime or security behavior changes. Legal/compliance impact is intentional and should be reviewed as a licensing decision, not as application risk.

Overview
Relicensing moves seedit from GPL-2.0-only to GPL-3.0-or-later so the app can be distributed with GPL-3.0 dependencies (e.g. @bitsocial/bitsocial-react-hooks).

package.json sets "license": "GPL-3.0-or-later". LICENSE replaces the GPLv2 text with the full GPLv3 license. User-facing copy is updated in README.md (badge), public/llms-full.txt (embedded README badge), and src/views/about/about.tsx (about-page license wording).

Reviewed by Cursor Bugbot for commit c596a08. Bugbot is set up for automated code reviews on this repo. Configure here.

Summary by CodeRabbit

  • Chores
    • Project license upgraded from GNU GPL v2 to GNU GPL v3.
    • All license references and metadata updated (badges, README, package manifest).
    • In-app and documentation text updated to reflect the new license wording and guidance.

seedit depends on @bitsocial/bitsocial-react-hooks (GPL-3.0-or-later), which is legally incompatible with GPL-2.0-only (no common license version). Move to GPL-3.0-or-later to resolve the conflict and align with the org's core stack (pkc-js, bitsocial-react-hooks).

- package.json: license -> GPL-3.0-or-later
- LICENSE: replace verbatim GPLv2 text with GPLv3
- README: license badge label

Relicensing authorized by cofounder / copyright holder.
@vercel

vercel Bot commented Jun 2, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
seedit Ready Ready Preview, Comment Jun 9, 2026 12:34pm

Request Review

@coderabbitai

coderabbitai Bot commented Jun 2, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: bf7203ac-a539-4aab-ae32-482cc4009ec0

📥 Commits

Reviewing files that changed from the base of the PR and between 9ba4808 and c596a08.

📒 Files selected for processing (2)
  • public/llms-full.txt
  • src/views/about/about.tsx
✅ Files skipped from review due to trivial changes (2)
  • src/views/about/about.tsx
  • public/llms-full.txt

📝 Walkthrough

Walkthrough

The project license is upgraded from GNU GPL version 2 to version 3. The main LICENSE document is replaced with the full GPLv3 text, and all project metadata declarations (README badge, package.json, LLM context, and about page copy) are updated to reflect GPL-3.0-or-later.

Changes

License Upgrade to GPLv3

Layer / File(s) Summary
GPLv3 License Document
LICENSE
LICENSE file replaced with complete GPLv3 text (2007), updating the preamble, all 17 sections of Terms and Conditions with GPLv3-specific legal provisions (patents, anti-circumvention), and the How to Apply template with revised instructions and removed GPLv2-specific examples.
Metadata and UI references
README.md, package.json, public/llms-full.txt, src/views/about/about.tsx
License badge in README, license field in package.json, generated LLM README entry, and displayed license text on the about page changed from GPL-2.0-only/GPL-2.0 to GPL-3.0-or-later.

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~45 minutes

Poem

🐰 A rabbit nods and hops in glee,

"GPL3 now covers you and me,"
Preamble fresh and clauses new,
Badges updated, docs in view,
Hooray — freedom renewed!" 🌱

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'Relicense: GPL-2.0-only → GPL-3.0-or-later' accurately and concisely summarizes the main change: updating the project's license from GPLv2 to GPLv3. It is specific, clear, and directly reflects the primary objective of the pull request.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/relicense-gpl-3.0-or-later

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.

❤️ Share

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

@coderabbitai coderabbitai Bot 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.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@package.json`:
- Line 7: Update the user-facing license text in the About component in
src/views/about/about.tsx (the About React component or exported About function)
so it matches package.json's "GPL-3.0-or-later" declaration; replace any
"GPL-2.0" wording (lines referencing GPL-2.0) with "GPL-3.0-or-later" or add a
clear note deferring the change and link to a tracked follow-up, ensuring UI and
metadata are consistent.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 7353a84a-d750-4a90-873f-d6d6014f7615

📥 Commits

Reviewing files that changed from the base of the PR and between 712253d and 9ba4808.

📒 Files selected for processing (3)
  • LICENSE
  • README.md
  • package.json

Comment thread package.json
@tomcasaburi

Copy link
Copy Markdown
Member Author

Addressed the valid CodeRabbit finding in c596a08 by aligning the About page license copy with package.json's GPL-3.0-or-later metadata and regenerating public/llms-full.txt. Local verification passed: corepack yarn install, yarn llms:generate, yarn build, yarn lint, yarn type-check, yarn doctor, and Playwright desktop/mobile checks in Chrome, Firefox, and WebKit. Remaining bot output is non-blocking/no actionable findings.

@tomcasaburi tomcasaburi merged commit 061cd08 into master Jun 9, 2026
8 checks passed
@tomcasaburi tomcasaburi deleted the chore/relicense-gpl-3.0-or-later branch June 9, 2026 12:40
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.

1 participant