Skip to content

Release notes

What's new in DV Forge, newest first. Each entry links to the guide pages that describe the feature in full.

November 2026

Triage

Your team can now take every failure signature from first sighting to closure inside DV Forge.

  • Triage lifecycle. Every signature has a status: untriaged, investigating, root-caused, tracked, resolved, regressed, muted, not a bug or waived. Open statuses move freely; closed and parked ones reopen. Tracked needs a bug, and waivers need a reason and a project admin's approval, with an optional expiry. Mutes can end on a set time. Expired mutes and waivers return to the queue on their own. The triage lifecycle
  • Regression detection. When a regression that ran after a fix hits a resolved signature, it moves to regressed and its assignee and watchers are alerted. Late uploads of older regressions don't reopen fixes.
  • The Triage page. Summary cards (open, closure %, unassigned open, live signatures), a filter builder with match all or any, private and shared saved searches, sorting, bulk actions on selected signatures with a per-signature report of anything that couldn't change, and CSV export of up to 50,000 rows. The triage queue
  • Working a signature. Assign owners, add project-wide labels (created inline), link a bug, watch, discuss in comments, attach files up to 10 MB (images get thumbnails), and follow a full activity timeline of who did what, including rules and the system. Working a signature
  • Filter language. One JSON filter language for the Triage page, saved searches, rules, previews, CSV export and the API, with relative times, "me", and labels by id or name. Filter language
  • Triage rules. Automate repeat decisions: on a new signature, a new hit, a recurrence, a regression, a finished root-cause run, or a finished regression, rules scoped by branch, saved search and conditions can set a status, assign, classify, label, link a bug, notify people, or start a root-cause run. Rules run in order, can stop later rules, act exactly once per event, and evaluate as of the regression's time. A live Would match preview and a full run log show what they do. Make this a rule turns a bulk action into a rule. Triage rules
  • Notifications. An in-app bell tells you when a signature is assigned to you, when one you own or watch regresses, when a rule notifies you, and when a root-cause run you launched, own or watch finishes or fails. Notifications

Signatures

  • Project-wide bucketing. Failures from every regression in a project are grouped into signatures across runs, so the same problem has one home no matter which regression or test hit it. Signatures
  • Merge, split and suggestions. Merge duplicates, split a signature that mixes problems, and act on suggested merges. Merge, split and suggestions
  • Bucketing settings and re-bucketing. Tune how messages are normalized for your project, preview the effect, and re-bucket existing failures. Bucketing settings
  • Recurrence. DV Forge notices when a signature comes back after a complete regression ran without it, and counts how often that happens.

Data planes

  • Keep raw logs in your network. Run a DV Forge data plane next to your simulation farm. It stores raw logs in your own storage, analyzes failures locally, and sends only structured results to DV Forge. It connects outbound only. Logs are fetched through it on demand when someone opens one. Data planes

Ingest

  • The dvforge CLI. Upload a regression's results from any machine or CI job, with resumable, idempotent uploads. The dvforge CLI
  • JUnit and logs. Send JUnit XML together with the simulation logs it refers to. Sending results
  • Simulator parsers. Failures are parsed from the log formats of common simulators. Simulators and log formats
  • CI examples. Ready-made examples for GitHub Actions, GitLab CI and Jenkins. CI integration
  • Standalone Linux binary. A single-file CLI for RHEL, Rocky and Alma Linux 8 and 9, with no Python install needed. Getting the CLI

Organizations, projects and access

  • Organizations, projects and roles. Sign-in by invitation; roles from viewer through member, triager, project_admin and org_admin. Projects, roles and tokens
  • API tokens. Project-scoped dvf_ tokens with read and ingest:write scopes for CI and scripts. API overview
  • Live updates. Pages refresh as uploads land and teammates triage, and the API streams the same events. API overview

Root-cause agent

  • Root-cause runs. Launch a root-cause run from a signature with Run root-cause, follow it live, and review its hypothesis. A person confirms the root cause, or a rule does it for you. Runs and hypotheses