Document 2.x → 3.x upgrade path - #72
Merged
Merged
Conversation
Adds the "Upgrading to 3.x from 2.x" section to UPGRADE.md (missing from the v3 release): Laravel 11 drop / framework floor, the new migrations, the destructive re-seed, the non-null native change, whitespace-normalized names and the additive State hierarchy API. Generalises the README upgrade pointer to cover any major bump. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Expands the 2.x -> 3.x guide with what consumers with their own foreign keys into Atlas tables need to know: - Path A (composer update + migrate) changes no rows -> zero risk to FKs. - Path B (re-seed) is safe for countries/states/cities/regions/subregions because PKs are seeded from the JSON id and the upgrade removes no existing ids, so FK targets survive. - Caveats: ON DELETE CASCADE during the disabled-FK delete, PostgreSQL privilege needs, and that currencies/languages/timezones ids are not preserved (reference them by natural code). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
eguiluz
previously approved these changes
Jul 15, 2026
Remove the `paths:` filters from the Tests and PHPStan workflows. With the filters, docs-only PRs never triggered these workflows, yet branch protection marks them Required — so those PRs got stuck forever on "Expected — Waiting for status to be reported". Running them unconditionally guarantees the required checks always report; the concurrency cancel-in-progress keeps redundant runs cheap. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
eguiluz
approved these changes
Jul 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Añade la sección Upgrading to 3.x from 2.x a
UPGRADE.md, que faltaba en la release v3. Cubre:admin_level/parent_id,nativeNOT NULL con backfill).atlas:states/cities/countries) — preserva IDs, sobrescribe ediciones locales, ventana de mantenimiento.nativeno-null, nombres normalizados (whitespace), API nueva de jerarquía (parent()/children()/topLevel()).También generaliza el enlace del README ("upgrading between major versions").
Doc-only. Recomiendo mergear antes de taggear 3.0.0 para que el tag incluya la guía.