August 11, 2026 — 31 country guides reviewed

  • Replaced the remaining template-only country sections with country-specific trunk-prefix, length and range guidance.
  • Added five reviewed normalization and negative cases to every country guide.
  • Added all 31 self-canonical guides to the sitemap and linked them from the homepage.
  • Kept third-party advertising limited to the original six high-traffic country guides.
  • Added regression checks for unique editorial notes, titles, descriptions and headings.

August 2, 2026 — editorial quality review

  • Added a public methodology describing source hierarchy, safety classifications and change control.
  • Published a 31-country safety matrix distinguishing documented creative-use examples from structural fixtures.
  • Added six reproducible E.164 normalization cases and explicit negative-test guidance.
  • Added manual editorial notes to the six country guides with demonstrated search use.
  • Marked unreviewed template country pages as noindex until each receives country-specific editorial work.
  • Added the GetPhoneNum Editorial Team byline and clearer maintenance ownership.

July 25, 2026 — ranking URL recovery

  • Restored the established Italy, Russia, Brazil, Bangladesh and France generator URLs as canonical pages.
  • Changed their shorter alternatives to one-hop permanent redirects.
  • Updated sitemap entries, homepage links, dataset links and structured data to use one canonical route.
  • Added homepage links to the five historically visible country generators.

July 20, 2026 — reusable dataset release

  • Published 31 country records as JSON and CSV.
  • Added a JSON Schema describing required fields.
  • Published a zero-dependency package with lookup helpers and tests.
  • Added source and fixture-safety fields so consumers can distinguish structure from contact safety.

July 19, 2026 — tool and guide rebuild

  • Released browser tools for validation, calling-code lookup, regex testing, E.164 formatting and bulk fixture export.
  • Added developer guides covering storage, extensions, international input, masking and testing.
  • Added About, Contact, Responsible Use and Privacy pages across the shared navigation.

Versioning policy

A date-based version changes when a record, safety classification, schema or published expectation changes. Wording and visual fixes that do not change the fixture contract may update a page without changing the dataset version. Consumers should pin a version for deterministic tests and review diffs before accepting an update.

Corrections require an official regulator, numbering administrator, ITU or standards reference. The editorial team does not change a national rule solely because an unsourced directory displays a different example.

Compatibility checklist for consumers

Before adopting a new dataset version, compare added and removed records, calling-code changes, national-length changes, safety-label changes and JSON Schema differences. A wording-only edit should not alter a test snapshot. A changed E.164 example or normalization rule should trigger the affected country suite and a deliberate review.

Applications that embed the CSV should also check column order and encoding. Applications using JSON should validate against the published schema rather than assuming every future field is mandatory. The zero-dependency package exposes the same records, so package, JSON and CSV consumers can compare one canonical fixture contract.

What the changelog does not claim

This page is an editorial history of GetPhoneNum, not an official record of national numbering-plan changes. A regulator remains authoritative for its plan. The log shows when this project reviewed or changed its representation, which source supported that decision and which tests should be revisited.

Repository commits provide the file-level diff, while this page explains the user-visible effect. Keeping both prevents a large generated diff from hiding the reason for a change.

How to report a correction

Use the public project contact channel and include the affected ISO country, current field, proposed field, source URL and why the source applies. Do not submit a real subscriber number as evidence. Security or privacy-sensitive reports should contain only the minimum information required to arrange a safer follow-up.