Skip to content

fix(packaging): canonical SPDX license expression (0.1.7) - #8

Merged
t0kubetsu merged 1 commit into
mainfrom
fix/spdx-license-metadata
Aug 12, 2026
Merged

fix(packaging): canonical SPDX license expression (0.1.7)#8
t0kubetsu merged 1 commit into
mainfrom
fix/spdx-license-metadata

Conversation

@t0kubetsu

Copy link
Copy Markdown
Collaborator

Problem

pyproject.toml declared license = "GPL-3.0". That is a deprecated SPDX
identifier: setuptools warns on it and PyPI validates license expressions, so the
correct spelling is GPL-3.0-only (or GPL-3.0-or-later). The license itself is
not changing — only its machine-readable form.

The build requirement was also under-constrained at setuptools>=68. This file
already relies on PEP 639 — a string license holding an SPDX expression, plus
license-files — which setuptools only implements from 77. Versions 68-76
reject a string license value, so a build in a clean environment could resolve
a setuptools too old to understand this metadata and fail. It works locally only
because pip's build isolation happens to fetch a current setuptools.

Change

  • license = "GPL-3.0-only"
  • requires = ["setuptools>=77", "wheel"]
  • Version bumped to 0.1.7 in pyproject.toml and the __init__.py fallback
    literal, with the matching CHANGELOG.md section and comparison links.

No source code, API or behaviour changed.

Verification

283 tests passed
ruff check     -> All checks passed!

The equivalent change was verified end-to-end on a built wheel
(License-Expression: GPL-3.0-only, dist-info/licenses/LICENSE present).

Part of an org-wide sweep: every module carried the same deprecated identifier.
Follows quantumvalidator, which shipped this in v0.6.4.

…loor

- license = "GPL-3.0-only" instead of the deprecated "GPL-3.0" SPDX
  identifier. Same license, canonical machine-readable spelling; setuptools
  warns on deprecated identifiers and PyPI validates them.
- Build requirement raised to setuptools>=77, the first release implementing
  PEP 639 (a string license holding an SPDX expression, plus license-files).
  setuptools>=68 allowed versions that reject a string license value, so a
  clean-environment build could resolve a setuptools too old for this
  metadata.

Version bumped to 0.1.7 with the matching CHANGELOG section and comparison
links. Verified: 283 tests pass, ruff clean.
@coderabbitai

coderabbitai Bot commented Aug 12, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@t0kubetsu, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 37 minutes

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: ASSERTIVE

Plan: Pro Plus

Run ID: 507e68f2-8abc-48a6-a00c-01253f75f2d2

📥 Commits

Reviewing files that changed from the base of the PR and between 7422ca6 and b0e8034.

📒 Files selected for processing (3)
  • CHANGELOG.md
  • chainvalidator/__init__.py
  • pyproject.toml

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

@greptile-apps

greptile-apps Bot commented Aug 12, 2026

Copy link
Copy Markdown

Greptile Summary

This PR corrects and synchronizes the package’s release metadata.

  • Replaces the deprecated GPL-3.0 identifier with the canonical GPL-3.0-only SPDX expression.
  • Raises the minimum setuptools version to 77 for PEP 639 metadata support.
  • Bumps the package and fallback versions to 0.1.7 and adds the corresponding changelog entry and comparison links.

Confidence Score: 5/5

The PR appears safe to merge with no actionable defects identified.

The packaging requirement now matches the metadata features in use, the SPDX expression is canonical, and all repository version declarations and release references are synchronized.

Important Files Changed

Filename Overview
pyproject.toml Updates the build backend requirement, canonicalizes the license expression, and bumps the package version consistently.
chainvalidator/init.py Synchronizes the source-tree fallback version with the new package version.
CHANGELOG.md Documents the packaging corrections and adds consistent 0.1.7 release comparison links.

Reviews (1): Last reviewed commit: "fix(packaging): canonical SPDX license e..." | Re-trigger Greptile

@t0kubetsu
t0kubetsu merged commit 1058a69 into main Aug 12, 2026
5 checks passed
@t0kubetsu
t0kubetsu deleted the fix/spdx-license-metadata branch August 12, 2026 14:17
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