Skip to content

fix(packaging): canonical SPDX license expression (0.3.4) - #25

Merged
t0kubetsu merged 2 commits into
mainfrom
fix/spdx-license-metadata
Aug 12, 2026
Merged

fix(packaging): canonical SPDX license expression (0.3.4)#25
t0kubetsu merged 2 commits 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.

Change

  • license = "GPL-3.0-only"
  • Version bumped to 0.3.4 in pyproject.toml and the __init__.py fallback
    literal, with the matching CHANGELOG.md section and comparison links.

This module already required setuptools>=83.0.0, so only the license
identifier needed fixing.

No source code, API or behaviour changed.

Verification

777 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.

- 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.

Version bumped to 0.3.4 with the matching CHANGELOG section and comparison
links. Verified: 777 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: 29 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: be31453b-1ffd-4757-befd-d78db7fbf1b8

📥 Commits

Reviewing files that changed from the base of the PR and between bf62940 and 6512e64.

📒 Files selected for processing (3)
  • CHANGELOG.md
  • mailvalidator/__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

The PR updates the package to version 0.3.4 and replaces the deprecated license identifier with the canonical GPL-3.0-only expression.

  • Synchronizes the project and fallback version literals.
  • Adds the 0.3.4 changelog section and comparison links.
  • Leaves prior Unreleased dependency changes outside the new release section.

Confidence Score: 4/5

The PR appears safe to merge, with a non-blocking release-note completeness issue in the changelog.

The package metadata and version sources remain consistent, but the new 0.3.4 section would omit dependency-floor changes shipped from the same revision.

Files Needing Attention: CHANGELOG.md

Important Files Changed

Filename Overview
pyproject.toml Correctly bumps the package version and uses a canonical SPDX expression consistent with the repository license.
mailvalidator/init.py Keeps the source-tree fallback version synchronized with project metadata.
CHANGELOG.md Adds correct 0.3.4 release links but does not move the existing Unreleased changes into the versioned section.

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

Comment thread CHANGELOG.md Outdated
The version bump left already-shipped changes under [Unreleased], so the
versioned section and its GitHub release notes would have omitted work
shipped from the same revision. CHANGELOG rule: never leave content under
[Unreleased] after bumping the version.

Caught by Greptile on the mailvalidator PR; the same defect was present in
this module.

@greptile-apps greptile-apps 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.

t0kubetsu has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.

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