Backup, migration, and upgrades

Before Operation

1. Save scripts, scenes, animations and configurations.
2. Confirms that Git workspace or backup can be restored.
3. Document the COCOS, PinK and key extension versions used by the project.
4. Saves the Platform Builder Tool and Path Configuration, but does not submit the key to the repository.

After Migration

1. Opens the item at a new location and waits for full initialization.
2. Checks resource references, script type errors and project configurations.
3. Run the minimum scene and complete build.
4. Once confirmed, the old copy is cleared.

version to upgrade borders

PinK has not yet published compatible matrices and automatic upgrade strategies between official versions. When there is no corresponding version of the migration description, do not overwrite the only copy of the project and do not assume that PinK and COCOS can be upgraded across versions.