With Digital.ai Deploy 26.1, large artifact handling has been improved.
Deploy can now handle artifacts of 2 GB or larger more efficiently by using a streaming approach instead of loading the full artifact into memory.

Why does this matter?

Because deployment reliability is not only about the deployment logic itself. Sometimes, a deployment can be correctly configured but still run into problems because the package is large and difficult to process efficiently.

This improvement helps reduce memory pressure and makes large artifact deployments more resilient, especially for teams working with bigger packages or running multiple deployments in parallel.

This may be especially relevant if your teams deploy:

large application archives
folder-based deployment packages
generated enterprise bundles
packages with many nested files
multiple large artifacts in parallel

• How do you currently manage large deployment artifacts?

• Do you split packages, tune memory settings, use external storage, or rely on the deployment platform to handle large artifacts automatically?

For technical details, check the Deploy 26.1 documentation.

Ask Release brings AI assistance directly into Release, helping teams get faster answers, understand release status more easily, identify potential issues, and reduce the manual effort involved in managing complex release processes.

Instead of spending time searching through releases, tasks, and status details, teams can simply ask questions and get useful insights in context. The goal is simple: help release teams move faster, make better decisions, and focus more on delivery.

If you are using the trial version or Release SaaS, you can try Ask Release today. Support for on-premises users is coming soon.

Learn more in the blog post:
https://digital.ai/catalyst-blog/ask-release-leverage-ai-to-streamline-devops/

Also new in this release: protection engine selection. You can now enable or disable individual engines independently, and choose which engine versions to run — useful for aligning protection configuration with your CI/CD pipeline or controlling when you adopt newly released engines.

One important note: the Android and iOS Native protection engines have been updated to a new Digital.ai-developed engine. AppAware is not yet supported on the new engine — support is planned for a future release.

Full release details are available in the download.

This release brings several exciting updates:

Now Supporting iOS 27 Beta – Test against iOS 27 Beta on real devices from Day Zero (June 8th). Teams can perform manual and automated testing across functional, performance, accessibility, and hardened application testing before the public release reaches users.

Support for Apple CarPlay Instrument Cluster – Automotive testing now extends beyond the main CarPlay display to include the Instrument Cluster. As teams begin automating CarPlay applications, cluster validation often remains a manual process. This gap is now closed by bringing the Instrument Cluster into the automated testing workflow.

Share Test Evidence Securely – Test results don't stay in QA. Developers, product teams, and external stakeholders all need visibility into testing outcomes. Secure sharing allows teams to share individual test results through protected links, making collaboration easier than ever.


26.5 also includes important platform improvements and bug fixes focused on stability, reliability, and overall testing experience.

Read the full 26.5 Release Notes

A question worth asking at the start of every beta season: how much time does your team actually have between "beta available" and "public release reaching users"?

For iOS, that window tends to close fast. And iOS upgrade rates mean issues that slip through don't stay contained for long.

Digital.ai Testing supports iOS 27 Beta on real devices — no additional configuration required, so teams can start validation now.

Read more →

Why this matters now - Many enterprises are shifting toward SaaS and hybrid models, but release operations are often where that transition stalls due to security and compliance expectations, data residency considerations, and the need for secure execution patterns. Release SaaS Platform is designed to help teams move forward confidently.  

What it is - A centralized SaaS control plane for release orchestration, including pipeline orchestration plus a release UI and dashboards. The goal is to provide a consistent orchestration and governance layer over existing toolchains, so teams don’t have to rip and replace their CI systems.  

What to expect (GA direction) 

• Full orchestration at enterprise scale with RBAC, auditability, and governance controls 

• Packaged integrations for common CI/CD, ITSM, and DevSecOps tools 

• Scaled SaaS infrastructure designed for reliability and operational simplicity 

Hybrid & multi-cloud support 

Release SaaS Platform supports hybrid and multi-cloud delivery by providing a central SaaS control plane that orchestrates releases across distributed targets—so teams can apply consistent governance and repeatable workflows across clouds, regions, and operating models. 

HA and DR are core to the platform’s operations to prevent orchestration downtime from slowing delivery. Release SaaS Platform is built to run reliably in resilient configurations and maintain continuity across HA/DR setups. 

Execution model (Phase 1 → Phase 2) 

Phase 1: Hosted runners (initial GA execution model) 
Hosted runners provide the fastest path to value—Digital.ai manages runner infrastructure, scaling, and reliability so teams can start orchestrating releases quickly with minimal operational overhead. 

Phase 2: On-prem runners (roadmap) 
For organizations that require execution inside restricted networks (e.g., regulated environments, data residency boundaries, isolated production systems), on-prem runners are planned in the next phase—extending the platform into a hybrid execution model while maintaining the same SaaS control plane and governance. 

• Default global page - the first page shown after login. Choose from Home, Folders, Tasks, Releases, or Templates.

• Default folder page - the page shown when opening a folder. Choose between Releases or Templates.

If you mostly review tasks (setting global landing page to Tasks) or design templates (setting folder landing page to Templates), these settings will save you clicks every session.

👉 Learn more in the docs

• Toggle View only configured to hide unconfigured connections and focus on what's actually in use.

• See the total number of connections and a count per connection type at a glance.

• Use the search bar to filter by connection type or name.

• Each connection now has a direct link you can copy and share with your team.

👉 Learn more in the docs

A few recent highlights:

From App Store to Clone: How AI Turns Your .ipa Into a Blueprint (May 15) AI is accelerating reverse engineering of iOS apps. What used to take days now takes hours.

Agentic AI Attacks: Agent Smith is Out of Retirement (April 6) Attackers are pushing the bounds of AI automation. Here's what that looks like in practice.

Fight Fire with Fire: Using AI to Fight AI (March 30) App attacks surged to 83% in early 2025. We break down how AI-powered defense is keeping pace.

When the Attacker Is the Client: Defending Against MitM Attacks (March 16) You've built a secure mobile app. But what happens when the attacker controls the connection?

Browse the full blog at https://digital.ai/learn/blog/

With Release 26.1, we’re excited to introduce Git Versioning Comparison Support — a powerful new feature that helps teams quickly compare versions, review changes, and identify updates directly from the Release UI.

🔍 What’s New?

Compare Git Versions Instantly

Users can now compare:

- Two Git versions side-by-side

- A Git version against the current state of a folder

This makes it faster than ever to understand what changed between versions without leaving the application.

✨ Key Highlights

📁 Enhanced File Explorer Comparison

The new comparison experience clearly highlights:

- Added files

- Removed files

- Modified files

This allows users to quickly identify impacted files and focus on what matters most.

🧩 Line-by-Line File Diff Viewer

Selecting a modified file opens a detailed comparison dialog showing differences between the two file.

Developers and release managers can now review changes with precision directly within the Release UI.

💡 Why It Matters

Git version comparison is critical for:

- Faster version validation

- Easier troubleshooting

- Improved collaboration between teams

- Better confidence before deployment

Release 26.1 streamlines the review process and reduces the need to switch between external tools.

📘 Want to learn more?

Check out the Release 26.1 release notes and detailed Version Comparison documentation here:
https://docs.digital.ai/release/docs/release-notes/release-notes-release#version-comparison