Add Release Step to Mapfixes

Quaternions commented

2025-08-12 00:15:14 +00:00

Owner

Using LoadAssetVersion control, mapfixes can be uploaded without affecting the live version. This integrates extremely well with the workarounds needed to fetch the LoadAssetVersion since they have many failure modes, but the map must not be re-uploaded, so cannot be rolled back to a pre-uploaded state. The same thing works for submissions: if the LoadAssetVersion fetch fails during the Releasing process, it can roll back to the Uploaded state. This also means that the possible states for mapfixes and submissions are identical.

Plan:

Add MapfixStatusReleasing state
Add MapfixStatusReleased state
Add SubmissionStatusReleasing state
Don't unify statuses - they are technically not the same.

Using LoadAssetVersion control, mapfixes can be uploaded without affecting the live version. This integrates extremely well with the workarounds needed to fetch the LoadAssetVersion since they have many failure modes, but the map must not be re-uploaded, so cannot be rolled back to a pre-uploaded state. The same thing works for submissions: if the LoadAssetVersion fetch fails during the Releasing process, it can roll back to the Uploaded state. This also means that the possible states for mapfixes and submissions are identical. Plan: - Add `MapfixStatusReleasing` state - Add `MapfixStatusReleased` state - Add `SubmissionStatusReleasing` state - Don't unify statuses - they are technically not the same.