Record Type
Record types control which picklist values and page layout a user sees, and their deployment depends entirely on picklist values already existing in the target org.
Definition
A record type lets different business processes on the same object show different page layouts and different subsets of picklist values, deployed as metadata alongside the picklist value sets it references. Deploying a record type requires every picklist value it activates to already exist on the target org's picklist field, standard or custom; if a picklist value was added as part of the same release, ordering matters, the field metadata has to land before the record type that depends on it, or the deployment fails on a missing value reference. Record type assignment to profiles is also metadata, but the default record type per profile is a separate setting that a metadata-only deployment can miss, leaving users able to create records under a record type that isn't set as their default, a source of confused support tickets about “the wrong page layout” more often than a deploy error. Our guide to managing Salesforce metadata covers dependency ordering in more detail.
How it works in Serpent
Serpent's dependency detection pulls in the picklist and profile metadata a record type actually depends on, not just the record type component itself, so ordering issues get caught before a deploy fails partway through. See release management in Serpent for how dependency-aware deployments work.
Start free. No credit card, no install, no commitment.
Set up in under 15 minutes. No DevOps hire needed.