buildMachine fields purchaseType, defaultPurchaseType, cores, memory, machineSelectionType removed
BreakingBreaking change
This is a breaking change — integrations that rely on the affected behaviour will need updates before the change rolls out.
What changed
The buildMachine object in both the team/user resourceConfig response schema has been significantly trimmed: purchaseType, defaultPurchaseType, cores, memory, and machineSelectionType fields have been removed, leaving only the default field. This is a breaking change for any client reading those fields from the API response. Additionally, the buildMachine object was relocated within the schema (position change only, no functional impact), and enum ordering for functionType and purchaseType was reordered (cosmetic for most validators, but strict enum-order validators may be affected).