Skip to content

Bump to 2.1.0, and point the banner at the release - #341

Merged
derek73 merged 3 commits into
masterfrom
release/2.1.0
Aug 7, 2026
Merged

Bump to 2.1.0, and point the banner at the release#341
derek73 merged 3 commits into
masterfrom
release/2.1.0

Conversation

@derek73

@derek73 derek73 commented Aug 7, 2026

Copy link
Copy Markdown
Owner

Summary

Release checklist step 1, plus the homepage banner.

file change
nameparser/_version.py VERSION = (2, 1, 0); PRE_RELEASE stays "" (no rc)
CITATION.cff version: "2.1.0"
README.rst the 📣 banner

CITATION.cff is the one the checklist calls out and nothing enforces: no test compares it to _version.py, so it drifts silently. Verified equal here.

The banner

Was leading with 2.0 compatibility and routing reports to the pinned migration issue:

📣 nameparser 2.0 is out. … anything the migration missed can be reported on the discussion issue <…/issues/284>__.

Now leads with what the release does, and sends people to the tracker:

📣 nameparser 2.1 adds East Asian name support. Chinese, Japanese and Korean names written in their own scripts are read family-first, unspaced Korean names are split against the census surname list, and CJK honorifics are recognized. See East Asian names <…/usage.html#east-asian-names>__.

Existing HumanName code keeps working through 2.x, and most 1.x code needs no changes. The migration guide <…/migrate.html>__ has the field-by-field map. Please open an issue <…/issues>__ for anything that parses wrong.

Two paragraphs so the 2.1 news leads and the 2.0 compatibility note stands on its own. The #east-asian-names anchor was verified present in the built usage.html. #284 is closed, having served the 2.0 migration.

What this PR deliberately does NOT do

docs/release_log.rst still says * 2.1.0 - Unreleased. Stamping a date before the tag exists means a wrong date if the merge slips past midnight, so that stays a tag-time step. Say the word if you'd rather have it here and I'll add it.

Verification

  • import nameparser__version__ 2.1.0, VERSION (2, 1, 0); matches CITATION.cff
  • python -m build --sdist → builds nameparser-2.1.0.tar.gz; twine check PASSED
  • python -m doctest README.rst → 16 pass
  • README is valid RST, no warnings
  • pytest 3065 passed; mypy and ruff clean; Sphinx HTML 0 warnings
  • Differential gate, both baselines: --baseline 1.4.0 107/0, --baseline 2.0.0 89 diffs / 0 unexplained / 0 Latin-only

One nice side effect of the bump: the gate's tree: line now reads 2.1.0 against a 2.0.0 baseline, so _check_tell's version half has real signal for that baseline instead of relying on the path check alone.

🤖 Generated with Claude Code

Release checklist step 1: VERSION and CITATION.cff's version field,
which nothing checks against each other, so they are easy to let drift.

The homepage banner led with 2.0 compatibility and sent reports to the
pinned migration issue. It leads with what 2.1 does now, and points at
the tracker rather than one thread; #284 served the 2.0 migration and
is closed.

The release log still says Unreleased. Stamping a date before the tag
exists risks a wrong one if the merge slips, so that is the tag-time
step.
@derek73 derek73 added this to the v2.1 milestone Aug 7, 2026
@derek73 derek73 added the docs Documentation fixes and updates label Aug 7, 2026
@codecov

codecov Bot commented Aug 7, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.48%. Comparing base (57d328c) to head (03951cd).
⚠️ Report is 4 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #341   +/-   ##
=======================================
  Coverage   98.48%   98.48%           
=======================================
  Files          41       41           
  Lines        2845     2845           
=======================================
  Hits         2802     2802           
  Misses         43       43           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Checklist step 2. Matches the existing format (no leading zero on the
day, as in 1.3.0 - July 5, 2026).

This assumes the tag lands today. If it slips, this line is the one to
correct.
@derek73 derek73 self-assigned this Aug 7, 2026
2.0 is still recent enough to lead with; the earlier version demoted it
to a compatibility footnote. The megaphone stays on 2.0, and the East
Asian note follows as its own paragraph.
@derek73
derek73 merged commit 49c381d into master Aug 7, 2026
9 checks passed
@derek73
derek73 deleted the release/2.1.0 branch August 7, 2026 07:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs Documentation fixes and updates

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant