Updates

Tracked runs created when a pull request is merged now record the commit as their trigger, as runs from push events already do. Before this change, these runs had no recorded trigger, so TF_VAR_spacelift_run_trigger fell back to git. It now reports vcs/commit.
This fixes downstream stacks in a dependency chain skipping their run when the upstream stack had no output changes.

Who’s affected: only you if your hooks or Terraform/OpenTofu code check this variable for git. Accept vcs/commit too:

contains(["git", "vcs/commit"], var.spacelift_run_trigger)

git remains a fallback for runs with no recorded trigger, such as proposed runs.
See Spacelift environment for all possible values.

A run is waiting on your confirmation in Spacelift. You're heads down in Slack or Microsoft Teams. You find out when someone asks why the deploy stalled.

Your day runs through Slack, Teams, and GitHub, not a Spacelift tab. Now your notifications can follow you there.

Link your Slack, Microsoft Teams, and GitHub accounts to your Spacelift identity from Personal Settings > External Accounts. Once you authorize the connection, notification policies can reference your linked account directly. A policy can mention the commit author when their tracked run fails, or ping whoever triggered a run the moment it needs their attention.

That also retires the hardcoded user map. Getting a mention right used to mean keeping a table like "bob": "U08MA4D50RY" inside your policy and updating it every time someone joined or left. Now the policy reads the linked ID straight from the input:

rego

author_identity.federations["slack-oauth"].id creator_session.identity.federations["slack-oauth"].id

If someone hasn't linked an account, the rule doesn't fire, so nobody gets a mention meant for someone else.

This feature is available on all plans and ready for you to take for spin, and tell us what you think! We love to hear from you.

Read the notification policy docs →

An unconfirmed run doesn't just disappear from existence. It sits there in Spacelift, waiting on a response, until someone remembers to deal with it. These can stack up and leave your run list pretty crowded. We just introduced a quality of life improvement for you.

Starting today, any run that doesn't reach a final state within 30 days of creation will expire and be removed from the queue, including runs that are simply waiting for approval or confirmation. Be sure to check the Runs to be Terminated widget on your Dashboard to see which runs will be expired within the next 7 days:

Finished runs and your existing infrastructure will not be affected in any way. If there's a run you still need, make sure it is approved, confirmed, or finished in some way before it hits the 30 day mark.