Desplega Release Notes — Week of May 25–June 1, 2026

This week’s release is about reducing QA fragmentation. Desplega now lets teams run API validation inside UI-driven tests, while the expanding qa-use CLI gives engineering organizations a more operational way to manage checks, schedules, and live reporting from the same platform story.

Across 7 commits in 2 repositories, the release combines a flagship workflow improvement, a substantial CLI surface expansion, and a targeted reliability fix that protects browser-session diagnostics when teams need them most.

Why does combining UI and API validation matter for release gates?

One authored flow now covers browser intent and backend proof, sharply shrinking handoffs between QA, platform, and API owners.

For engineering leaders, the key shift is not just convenience. It is the removal of a structural blind spot that often appears between end-to-end UI coverage and API-level assertions. When those checks live in separate systems, release gates become slower to debug, harder to trust, and more dependent on cross-team coordination.

Desplega’s new embedded API-check step brings that validation directly into the business flow being tested. A sign-in journey can now assert the browser result and the backend contract in the same path, which means faster feedback loops, fewer orphaned checks, and a cleaner story for teams that need traceable release confidence.

name: api-check-step-example
variables:
  env:
    value: staging
    type: custom
    lifetime: test
    context: check
steps:
  - type: extended
    name: Run authentication API check
    step_id: run-auth-check
    action:
      action: api_check
      value:
        check_id: 00000000-0000-0000-0000-000000000000

How does qa-use change operational QA for growing teams?

Checks and schedules can now be managed as first-class operational assets, making QA easier to standardize across environments.

The second theme in this release is operational control. qa-use moved further beyond test execution into day-to-day QA operations, adding first-class workflows for creating checks, building schedules, and triggering remote runs with seeded variables. That matters when teams want repeatable quality processes without forcing every workflow through the UI.

In practical terms, this gives platform and QA leads a cleaner way to operationalize routine validation, especially for shared environments, smoke chains, and recurring release checks. The CLI becomes the command surface for standardization, not just a utility for individual developers.

qa-use check create \
  --name "Auth token" \
  --app-config APP_CONFIG_ID \
  --config auth-check.json \
  --alias auth \
  --capture token=$.access_token

qa-use check-schedule run SCHEDULE_ID \
  --var env=staging \
  --var claim_id=123

• Teams can define checks and schedules from the CLI without inventing side-channel workflows.
• Remote schedule runs make repeatable QA easier to seed across staging and shared environments.
• Live checks QA reporting increases visibility into what is running and what needs attention.

Reliability hardening that protects production evidence

The BrowserSession console-log sanitation fix is a smaller change, but it is exactly the kind of reliability work mature teams look for. Stripping NUL bytes from stored console logs prevents edge-case corruption in a part of the system that often becomes important only when a release is under investigation.

Desplega backed that fix with dedicated regression coverage, which is the right signal for buyers evaluating whether a platform takes production quality seriously. New capabilities matter, but so does the integrity of the artifacts your team depends on when something breaks late in the release cycle.

What comes next for Desplega?

This release points in a clear direction: Desplega is converging test authoring, execution, and QA operations into one workflow model. Expect the next cycle to build further on that foundation with deeper operational surfaces, stronger release-gate ergonomics, and more ways to keep browser and API confidence inside the same system of record.

For CTOs and engineering leaders, that is the strategic takeaway. The platform is not just adding isolated features; it is reducing the number of places your team has to switch context in order to ship with confidence.