Skip to content

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

Open
tomcasaburi wants to merge 1 commit into
masterfrom
chore/relicense-gpl-3.0-or-later
Open

Relicense: GPL-2.0-only → GPL-3.0-or-later#16
tomcasaburi wants to merge 1 commit into
masterfrom
chore/relicense-gpl-3.0-or-later

Conversation

@tomcasaburi
Copy link
Copy Markdown
Member

@tomcasaburi tomcasaburi commented Jun 2, 2026

Why

bitsocial-telegram-bots is GPL-2.0-only but depends on @plebbit/plebbit-js (= pkc-js, GPL-3.0-or-later). GPL-2.0-only is legally incompatible with GPL-3.0-or-later. Moving to GPL-3.0-or-later resolves the conflict.

Changes

  • package.json: licenseGPL-3.0-or-later
  • LICENSE: GPLv2 text → GPLv3
  • README.md: License section

Authorized by cofounder / copyright holder. Licensing strategy, not legal advice.


Note

Low Risk
Documentation and SPDX metadata only; no code paths or deployment behavior change, though downstream distributors must comply with GPLv3 terms.

Overview
Relicensing aligns the project with its GPL-3.0-or-later dependency (@plebbit/plebbit-js), replacing the prior GPL-2.0-only declaration that is incompatible with GPLv3.

package.json now declares "license": "GPL-3.0-or-later". LICENSE is replaced with the full GPLv3 text (including sample notices referencing version 3). README.md License section is updated to GPL-3.0-or-later. No application source or runtime behavior changes.

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

Summary by CodeRabbit

  • Chores
    • Updated project license from GPL-2.0 to GPL-3.0-or-later, including license documentation and package metadata.

bitsocial-telegram-bots depends on @plebbit/plebbit-js (pkc-js, GPL-3.0-or-later), which is legally incompatible with GPL-2.0-only. Move to GPL-3.0-or-later to resolve the conflict.

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

Relicensing authorized by cofounder / copyright holder.
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Jun 2, 2026

Review Change Stack

📝 Walkthrough

Walkthrough

This PR upgrades the project's license from GPL v2 to GPL v3. The LICENSE document is replaced with GPLv3 text, and license metadata in README.md and package.json are updated to reflect the new version.

Changes

GPL v2 to v3 License Upgrade

Layer / File(s) Summary
GPL v3 license document
LICENSE
LICENSE file replaced with GPLv3 text, including updated version header, Terms and Conditions sections reorganized for GPLv3, revised NO WARRANTY and liability clauses, and the "How to Apply These Terms to Your New Programs" template updated from GPLv2 to GPLv3 format.
License metadata in README and package.json
README.md, package.json
License declarations updated from GPL-2.0 and GPL-2.0-only to GPL-3.0-or-later in both project metadata files.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐰 From GPL-2 to GPL-3 we leap,
Legal scrolls now run ever deep,
Metadata synced with terms so fine,
License and declarations align!
The rabbit approves of this upgrade divine. ✨

🚥 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 clearly and concisely summarizes the main change: updating the project license from GPL-2.0-only to GPL-3.0-or-later, which directly corresponds to the core objective and all file changes.
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 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.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
package.json (1)

18-18: ⚠️ Potential issue | 🔴 Critical | ⚡ Quick win

Fix license mismatch: pinned @plebbit/plebbit-js is GPL-2.0-only, not GPL-3.0-or-later.

At commit 692ec349f01aa6d8e939ff1d6d07315ab92e4099, plebbit-js’s package.json declares GPL-2.0-only, and the LICENSE file indicates “GNU GENERAL PUBLIC LICENSE Version 2, June 1991”, so it doesn’t support the stated GPL-3.0-or-later premise for the relicense.

🤖 Prompt for 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.

In `@package.json` at line 18, The dependency entry for "`@plebbit/plebbit-js`"
pinned to commit 692ec349f01aa6d8e939ff1d6d07315ab92e4099 incorrectly assumes
GPL-3.0-or-later; that commit's package.json and LICENSE are GPL-2.0-only.
Update the package.json dependency handling: either replace or repoint the
"`@plebbit/plebbit-js`" entry (the git URL with commit
692ec349f01aa6d8e939ff1d6d07315ab92e4099) to a version/commit that is actually
GPL-3.0-or-later, or explicitly mark it as GPL-2.0-only in our metadata and
remove any relicense claims; alternatively remove/replace the dependency with a
compatible-licensed package. Ensure changes reference the same package name
"`@plebbit/plebbit-js`" and the offending commit hash when committing the fix.
🤖 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.

Outside diff comments:
In `@package.json`:
- Line 18: The dependency entry for "`@plebbit/plebbit-js`" pinned to commit
692ec349f01aa6d8e939ff1d6d07315ab92e4099 incorrectly assumes GPL-3.0-or-later;
that commit's package.json and LICENSE are GPL-2.0-only. Update the package.json
dependency handling: either replace or repoint the "`@plebbit/plebbit-js`" entry
(the git URL with commit 692ec349f01aa6d8e939ff1d6d07315ab92e4099) to a
version/commit that is actually GPL-3.0-or-later, or explicitly mark it as
GPL-2.0-only in our metadata and remove any relicense claims; alternatively
remove/replace the dependency with a compatible-licensed package. Ensure changes
reference the same package name "`@plebbit/plebbit-js`" and the offending commit
hash when committing the fix.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: de6ed04c-f6f8-4e94-885d-f95d16333892

📥 Commits

Reviewing files that changed from the base of the PR and between b5ab726 and 1e47d6f.

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

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