Product Decisions This Supports

Build vs. buy for GEDCOM parsing and export: v4.2.0 strengthens the case for adopting this package instead of building in-house, especially if your roadmap includes GEDCOM-X interoperability.
Roadmap prioritization: the new UID/_UID support across all GEDCOM record types with GedcomX export enables standards-compliant data portability features; the WIP GEDCOM-to-GEDCOM-X mapping is a leading indicator that full GEDCOM-X support is progressing but not yet production-ready.
Feature scoping: decide whether to ship basic GEDCOM import/export now (stable) and defer full GEDCOM-X mapping until PR #95 is complete.
Use cases: genealogy SaaS platforms, family history apps, archival tools, and any Laravel product needing to ingest or emit GEDCOM data and expose UIDs for record identity.

When to Consider This Package

You need GEDCOM 5.5.1 parsing and export inside a Laravel/PHP application.
You want UID/_UID support for all record types with GedcomX export—this is now available and useful for identity and interoperability.
You are evaluating GEDCOM-X mapping but can tolerate a WIP implementation (PR #95) and plan to monitor or contribute.
Look elsewhere if you require a fully production-ready GEDCOM-X mapping today, need a non-Laravel stack, or require commercial support/SLAs not offered by this package.

Executives: This release advances standards compliance (UID support) and signals movement toward GEDCOM-X, reducing our build risk for genealogy data interoperability. Adopt the stable UID/export features now; treat GEDCOM-X mapping as a watch item until the WIP PR matures.
Engineering: v4.2.0 adds UID/_UID support across all record types with GedcomX export and introduces WIP GEDCOM-to-GEDCOM-X mapping. Integrate the stable export path, isolate GEDCOM-X mapping behind a feature flag, and track PR #95 before committing to full GEDCOM-X workflows.