We know the feeling: you’ve improved a core stack, but you’re hesitant to push it because you don't want to break dozens of stable production components.

 Today, we are bridging the gap between rapid innovation and rock-solid stability with the release of 

This isn't just a minor update: it's a fundamental shift in how you manage the lifecycle of your infrastructure.

❓ The "Why": Governance without the Handbrake

In the past, updating a stack was often an "all or nothing" affair. 

 introduces a decoupled workflow where platform teams can iterate at light speed while application owners move at their own pace.

 You can now ensure that production environments only use "Certified" tags, while development teams experiment with bleeding-edge branches. 

 No more forced migrations. You decide when a component is ready to move to the next version, reducing the risk of downtime and "day-to-day" friction. 

 Stop wondering who is using which version of your Stack. See your entire "stack footprint" at a glance.

💡 Real-World Use Cases to Get You Excited

How will this change your workflow? Here are a few ways you can start using it today:

We can't wait to see how you use this to scale your infrastructure. To get started, you'll just need to make a quick update to your 

 to make your Git resources version-aware.

Cycloid changelog

Stack Versioning: Tame your infra lifecycle