new-export-version

Game export schema versioning is automated by generating a new per-version schema file, its migration module, and associated tests to enforce backward compatibility. This coordinates version bumps across export producers, loaders, and migrations.

Adding a new game export format version involves defining a versioned schema file, writing the migration logic, and updating test coverage. This ensures forward compatibility when evolving the export format during development workflows.

Backward compatibility for game export schemas is maintained by generating dedicated migration scripts alongside new schema versions. Migration logic handles data transformation, while updated tests validate schema rules and migration round-trips.

The export migration workflow integrates with existing tooling by enforcing versioned schema handling and test coverage checks. It coordinates with schemas, migration scripts, and puppeteer tests to validate schema changes and migration round-trips.

Create a new export version with migrations when evolving the export format requires preserving backward compatibility for previously exported games. Modifying the current schema directly risks breaking existing exports without dedicated migration logic.