[18.0][FIX] ptplus_accounting: keep the taxonomy remap versioned 17.0.5.1.0 - #5
Open
eantones wants to merge 1 commit into
Open
[18.0][FIX] ptplus_accounting: keep the taxonomy remap versioned 17.0.5.1.0#5eantones wants to merge 1 commit into
eantones wants to merge 1 commit into
Conversation
….5.1.0 The vendor re-published the 17.0.5.1.0 taxonomy remap as 18.0.5.1.0, so every database coming from 17 re-runs it on an already-migrated model: account_prefix arrives NULL, 'None' matches nothing and the wipe-on-no-match erases l10n_pt_taxonomy_id from every account (W1, 2026-07-19). Renaming the migration back to the 17 series keeps it from ever re-firing on a database already past it. Pure rename, no content change. Re-parented on exo snapshot 518e6833 (2026-08-05): the mirror is bot-published with force-pushed orphan snapshots per release, the remap directory is byte-identical to the previous snapshot 0164319.
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
1 participant
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.
Replaces #1, which GitHub auto-closed when the fix was re-parented onto the vendor's new snapshot (the mirror is bot-published with force-pushed orphan snapshots per release) and refused to reopen afterwards.
Same single commit as #1, re-created on snapshot 518e6833 with the fork base resynced first: the vendor re-published the 17.0.5.1.0 taxonomy remap as 18.0.5.1.0, so every database coming from 17 re-runs it on an already-migrated model and the wipe-on-no-match erases l10n_pt_taxonomy_id from every account (W1, 2026-07-19). Renaming the migration back to the 17 series keeps it from ever re-firing. Pure rename, no content change.
Local-only: carries the fix for our aggregated builds; the defect report goes to the vendor separately.