You can now define reusable deployment progressions for your environments and enforce them across your org, projects, or components.
Previously, there was no built-in way to standardize the order in which code moves through environments. Teams had to manage promotion paths manually, with no guardrails to ensure deployments followed the right sequence.
Now, you can:
- Create named hierarchy templates (e.g., Development → Staging → Production) in your org settings under Deploys.
- Set an environment hierarchy as the org-wide default, and assign hierarchies to specific projects or components.
- Once assigned, version promotions follow that path automatically, and you can see each environment’s deployment status at a glance on the version promotion page.
What’s changed:
- Create and manage environment hierarchy templates from org settings under Deploys
- Set a hierarchy as the org default or assign it at the project or component level
- Version promotion pages now show each environment in the hierarchy with its current deployment status and version
Teams deploying across multiple environments can now standardize promotion paths, reduce manual coordination, and quickly see where any version currently stands across all environments.