chore(deps): bump pycountry from 24.6.1 to 26.2.16

[dependabot]

Bumps pycountry from 24.6.1 to 26.2.16.

Changelog

Sourced from pycountry's changelog.

26.2.16 (2026-02-16)

• Dropped support for end-of-life Pythons 3.8 and 3.9.

• Added explicit support for Python 3.13 and 3.14.

• Updated to iso-codes 4.20.1.

• Added support for matching initials in countries.search_fuzzy. For example, results for countries.search_fuzzy("UK") will now include GB (United Kingdom).

• Fixed subdivisions.add_entry and subdivisions.remove_entry, which would previously render the country_code index of subdivisions unusable causing subdivisions.get(country_code=...) to return a malformed result. Fixes issue #281.

Commits

• 4ba3951 Merge pull request #297 from zware/bump_for_release
• 88b0238 v26.2.16
• f2ded46 Merge pull request #296 from zware/updates
• 3aafdea Update pre-commit and poetry.lock
• bb80ba7 Merge pull request #295 from zware/publishing
• 7b25dcd Add workflow for PyPI publishing
• d2eed3d Merge pull request #292 from pycountry/pre-commit-ci-update-config
• ef67683 [pre-commit.ci] pre-commit autoupdate
• f5750fd Merge pull request #286 from zware/add_entry_index_fix
• c713c76 Fix subdivisions.{add,remove}_entry
• Additional commits viewable in compare view

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[rtibbles]

@dependabot rebase

[rtibblesbot]

Dependency update review for pycountry 24.6.1 → 26.2.16.

CI checks are pending (branch was just rebased via @dependabot rebase). Analysis below is based on changelog and code inspection — merge once CI passes.

Dependency Update Review

Package: pycountry 24.6.1 → 26.2.16
Semver risk: Multi-major by number, but pycountry uses date-based versioning (YY.M.DD). This is a single release — there are no intermediate versions between 24.6.1 and 26.2.16 in the changelog.
Dependency type: Production (used in loadconstants.py management command for country data)
CI status: Pending (branch freshly rebased)

Changelog Analysis

Sources consulted:

• HISTORY.txt
• PR body (release notes for 26.2.16)

Breaking changes: None.

Notable changes:

• Dropped Python 3.8 and 3.9 support — project uses Python 3.10 (confirmed in CI workflows), unaffected.
• Updated to iso-codes 4.16.0 → 4.20.1 (data update; Kosovo is added manually via countries.add_entry, so not impacted).
• Fixed subdivisions.add_entry / subdivisions.remove_entry index corruption bug (#281) — project uses countries.add_entry, not subdivisions, so this is a safe bystander fix.
• Added initials matching to countries.search_fuzzy (e.g. "UK" → GB) — project does not appear to use search_fuzzy, so no impact.

Side-effect changes in this PR

The diff also removes [grpc] extras from two transitive dependencies:

• google-api-core[grpc] → google-api-core
• googleapis-common-protos[grpc] → googleapis-common-protos

This is a uv lockfile regeneration artifact, not a pycountry change. It's safe: error_reporting.py explicitly passes _use_grpc=False, so gRPC transport is intentionally unused.

Compatibility Assessment

• Project uses affected APIs: countries.add_entry (unchanged), pycountry.countries iterable (unchanged)
• Peer dependency changes: None
• Code changes required: None
• Prior failed attempts: None found in PR comments (maintainer only posted @dependabot rebase)

Recommendation

APPROVE once CI passes — no breaking changes, project is on a supported Python version, and the grpc extras removal is safe.

---

@rtibblesbot's comments are generated by an LLM, and should be evaluated accordingly

How was this generated?

Reviewed the pull request diff checking for:

• Correctness: bugs, edge cases, undocumented behavior, resource leaks, hardcoded values
• Design: unnecessary complexity, naming, readability, comment accuracy, redundant state
• Architecture: duplicated concerns, minimal interfaces, composition over inheritance
• Testing: behavior-based assertions, mocks only at hard boundaries, accurate coverage
• Completeness: missing dependencies, unupdated usages, i18n, accessibility, security
• Principles: DRY (same reason to change), SRP, Rule of Three (no premature abstraction)
• Checked CI status and linked issue acceptance criteria
• For UI changes: inspected screenshots for layout, visual completeness, and consistency

[rtibbles]

This seems safe to merge as long as tests pass.