
Note: Full release notes can be found here.
Scalr AI is now available to assist your users with intelligent error analysis and approval assistance. This automatically reviews errored runs to identify root causes and suggest resolution steps, while also providing AI-generated plan summaries that help approvers make informed decisions about infrastructure changes. Enable Scalr AI from your account integrations page to start leveraging AI-powered troubleshooting today. See the docs and FAQ on this. This feature is currently considered experimental.

Streamline your developer workflow with the new Scalr plugin for Backstage, the open-source developer portal platform. Teams can now manage their Terraform infrastructure directly from Backstage, viewing workspace status and initiating runs without leaving their centralized portal. The plugin is available in the official Backstage catalog and ready for installation today. This feature is currently in beta.

Scalr AI now automatically generates explanations with potential resolutions for failed VCS runs and streams them directly to pull request comments. This eliminates the need to manually trigger AI explanations or switch back to Scalr, providing instant insights into run failures right where you review code. All VCS providers are supported. (June 11th, 2025/8.208.0)

Scalr now generates AI dry-run summaries by evaluating the plan and giving an overview. Previously, this was only available during the apply approval phase. If AI is enabled in the account and the AI button has been clicked in the workspace previously, it will automatically appear in the workspace. (June 11th, 2025/8.208.0)

Scalr now includes AI-generated Terraform plan summaries directly in pull request comments. This enhancement helps reviewers quickly understand infrastructure changes, accelerate code reviews, and catch critical issues faster without leaving their VCS workflow. All VCS providers are supported. (June 11th, 2025/8.208.0)

Scalr Apply pull request comments now display clear approve/decline commands (/scalr approve, /scalr decline) instead of outdated run-triggering commands, making it easier to manage Terraform runs directly from pull request comments. This change removes outdated options like /scalr apply and /scalr apply -force, which should only be available during the plan phase, not for the apply approval. Use the new commands with optional workspace specifications and reasons, such as:
"/scalr approve -reason='Approved from PR'"
"/scalr decline -workspace-id=ws-xxxx -reason='Your reason here'"
(June 5th, 2025/8.207.0)
Scalr now monitors active audit log integrations and sends email alerts to the Scalr account owner when previously working integrations fail, including failure details to enable quick resolution. This prevents compliance blind spots by ensuring immediate notification of logging failures, helping maintain regulatory requirements like SOC 2 and ISO 27001. Monitoring is automatically enabled for all active integrations with no setup required—alerts include integration details, failure timestamps, and error descriptions. (June 5th, 2025/8.207.0)
We've updated permissions handling for the runs queue access to ensure consistent behavior across environment and account levels. This update was made to make environment-level and account-level runs queues now follow the same permission model. To ensure continued access to the runs queue functionality, verify that users have the appropriate permissions:
Environment-level Runs Queue:
environments:read-runs-queueenvironments:readworkspaces:readAccount-level Runs Queue:
runs-queue:readenvironments:readworkspaces:readRuns History (any level):
environments:readworkspaces:read(June 2nd, 2025/8.206.0)
Scalr now displays private module registry namespaces directly in the UI, allowing users to browse, filter, and search modules by their associated account or environment namespaces. This improves module discoverability by surfacing previously API-only namespace structure, with visibility automatically scoped to user permissions and no setup changes required. (June 19th, 2025/8.210.0)

