-
Notifications
You must be signed in to change notification settings - Fork 0
[M22.3] Verify v0.2.x saves migrate cleanly to v0.3.x #49
Copy link
Copy link
Open
Labels
area:saveSave/load, migrations, storage, abandon campaign, or compatibility.Save/load, migrations, storage, abandon campaign, or compatibility.channel:alphaTargets alpha promotion, playtest, pre-release, or alpha build work.Targets alpha promotion, playtest, pre-release, or alpha build work.priority:p1High priority: milestone blocker or serious player/contributor impact.High priority: milestone blocker or serious player/contributor impact.type:choreMaintenance, cleanup, dependency, or refactor with no player-facing change.Maintenance, cleanup, dependency, or refactor with no player-facing change.
Milestone
Description
Metadata
Metadata
Assignees
Labels
area:saveSave/load, migrations, storage, abandon campaign, or compatibility.Save/load, migrations, storage, abandon campaign, or compatibility.channel:alphaTargets alpha promotion, playtest, pre-release, or alpha build work.Targets alpha promotion, playtest, pre-release, or alpha build work.priority:p1High priority: milestone blocker or serious player/contributor impact.High priority: milestone blocker or serious player/contributor impact.type:choreMaintenance, cleanup, dependency, or refactor with no player-facing change.Maintenance, cleanup, dependency, or refactor with no player-facing change.
Test that saves written at v0.2.0-alpha load correctly in the v0.3 build. If the M21 JSON migration changed the internal data shape, ensure the migration runner handles any affected save fields. Add a v0.2.x fixture if one doesn't exist.