sf-deployment-constraints

What problem does it solve?

Prevent risky, partial, or failed Salesforce deployments by enforcing a validation-first workflow, adequate test coverage, correct metadata ordering, and rollback readiness so teams avoid broken production state and deployment-induced outages.

Core Features & Use Cases

• Validation-first enforcement: Require validation-only deploys before any real deploy and prohibit quick-deploy without an explicit job id when conditions aren't met.
• Test coverage and test-level gating: Mandate appropriate test-level flags for shared orgs and production and ensure aggregate org coverage meets the production threshold.
• Dependency ordering and safe packaging: Recommend and enforce an ordered deployment sequence (objects, fields, layouts, Apex, permission sets, profiles last) and separate Profile deployments.
• Rollback and snapshot readiness: Require pre-deploy snapshots for destructive changes and prescribe rollback strategies like git revert, single-file restore, or package version rollback.
• Use Case: Use when promoting code from CI/UAT to production to prevent silent test omissions, broken metadata references, and unrecoverable destructive changes.

Quick Start

Validate the package with a validation-only deploy using the appropriate test level, review the validation report, and then quick-deploy by job id once tests and dependencies are confirmed.