Build settings, signing, entitlements, CI, dependencies, and release configuration
A release configuration is an auditable build input. It selects endpoints, identifiers, capabilities, optimization, diagnostics, and signing without embedding credentials in source control.
Design the boundary
- The composition root reads validated nonsecret settings. Secrets enter through protected CI or developer storage at the narrow tool that needs them.
- Pin package versions and review resolved dependency changes. Keep capabilities and entitlements minimal per target.
- Archive the same scheme and configuration exercised by the release lane. Preserve logs, symbols, test results, and provenance.
- Signing proves executable identity and authorized entitlements. It does not prove product behavior.
Validation boundary
No archive, signing identity, provisioning profile, App Store connection, or release CI lane was available.
Series navigation
- Previous: Part 84: Instruments, responsiveness, energy, launch, and networking
- Next: Part 86: TestFlight, App Store review, launch, observability, and evolution
- Series index: Zero to iOS Hero