CHANGELOG

Small changes. Better testing.

Stay up to date with new features and improvements.

May 26, 2026Dashboard 2.30.1

Fix bot author label on template deployments

Fixed an issue where deployments from a new procedure template showed the TofuPilot bot as an "External Contributor".

  • Bot-authored template commits now show a "TofuPilot Bot" badge.
May 26, 2026Dashboard 2.30.0Docs

Import runs from OpenHTF, WATS, and CSV files

Bring your existing test reports into TofuPilot without writing any API code. Drag a file into the dashboard and it becomes a run, so you can backfill history from benches and testers you already have.

  • Added file import in the dashboard for OpenHTF JSON logs and WATS reports, auto-detected on upload, plus CSV files where you map your columns to fields once and save the mapping as a preset to reuse on every later file. Batch import handles many files at once.
  • Added duplicate detection, so re-importing the same file links to the existing run instead of creating a copy.
  • Improved the import and list pages with an inline drag-and-drop dropzone at the top of the import table, quick add buttons on the runs and units lists, and a clearer download icon for export.
May 22, 2026Docs 2.3.10

Rewrite incremental migration guide

The /docs/incremental-migration page is now structured around vertical and horizontal migration strategies, with an animated diagram that shows each one in action.

  • Reframed the page around incremental migration benefits, disadvantages of one-time migrations, and three strategies: vertical (one integration layer at a time across procedures), horizontal (one procedure end-to-end), and hybrid.
  • Added an animated grid that plays vertical fill first, pauses, then horizontal fill so the difference is visible at a glance.
May 22, 2026Dashboard 2.29.12Website 0.10.117Docs 2.3.9

Refresh doc links for docs v2.0

Following the docs v2.0 release, every doc link across the dashboard, marketing site, and docs site has been audited and pointed at the current pages so users land on the right place instead of a stale route.

  • Repointed dashboard empty states, deployment pages, and OpenAPI references to the new docs IA.
  • Updated landing footer, navbar, connector, and self-hosting links so the site sends visitors to the right docs.
  • Fixed internal docs redirects after the data-model rename and refreshed SDK readmes with the new per-language guide links.
May 21, 2026Docs 2.3.6

Rewrite test and device data model pages

Both fundamentals data model pages were rewritten into one consistent reference with updated diagrams.

  • Rewrote the test and device data model pages with a uniform per-concept format.
  • Refreshed the animated diagrams and added a Schema reference section with direct links to REST API endpoints.
May 21, 2026Docs 2.3.4

Animate test and device data model diagrams

Two new animated tree diagrams make the test and device data models easy to read at a glance, with example values and pass/fail states streaming in as each entity is highlighted.

  • Added an animated tree on the Test Data Model page (Procedure, Run, Phase, Measurement, Validator, Log, Attachment) with live example values and a PASS validator outcome
  • Added an animated tree on the Device Data Model page (Part, Revision, Unit, Sub-unit, Batch) with the Batch drawn as a dashed connector to signal that batches are optional and cross-cutting
  • Renamed the underlying pages to Test Data Model and Device Data Model and updated every link across the docs
May 21, 2026Docs 2.3.3

New Test Lifecycle page with animated diagram

A new fundamentals page maps the four stages of a hardware test on TofuPilot end to end.

  • Added a "Test Lifecycle" page covering author, deploy, run, and analyze with an animated diagram of the cycle
  • Listed the three authoring paths (TofuPilot Framework, supported framework, custom test code) at every stage so it is clear how each one moves through the lifecycle
May 21, 2026Docs 2.3.2

Add Run, Log, and Unit explorers

Three new explorer pages give the table-driven workflows you live in every day their own home in the docs.

  • Added Run, Log, and Unit explorer pages under Analytics, each covering columns, filters, saved views, export (CSV and JSON, visible or selected rows), metadata, and role-based permissions
  • Renamed the station Operator UI page to Remote UI to avoid confusion with the framework's per-phase operator UI components
  • Rewrote the docs landing around the actual journey: build, deploy, operate, observe, collaborate, integrate, then explore
  • Added a "Get support" section on the landing with direct links to Discord, support email, trainings, and custom integrations
May 21, 2026Docs 2.3.0

Documentation 2.0

A re-architected documentation site with cleaner navigation and dedicated space for the new surface areas TofuPilot ships against.

  • Reorganized the sidebar around what you actually use day-to-day. Top groups now flow from "Getting started" and "Fundamentals" into product surfaces: Frameworks (TofuPilot, OpenHTF, Pytest, Robot), API & SDKs (Python, C#, Rust, C++, MATLAB, REST), CLI, AI, Analytics, Deployments, Integrations, Inventory, Station, Access, Security, Pricing, Self-hosting
  • Replaced the flat dump of pages with grouped sections, so framework-specific guidance, SDK references, and integration setups each live under their own dedicated group instead of sharing one bucket
  • Added per-resource sub-sections so growing surface areas (every CLI command, every REST endpoint, every Station toggle) have their own page instead of being concatenated
  • Added a Preview badge and banner so features still rolling out (AI, Slack, InvenTree, Reports, Insights, Failure Analysis, Rolling Rollout, Instant Rollback) are clearly flagged
May 20, 2026Dashboard 2.29.8

Fix linking GitLab repos in nested subgroups

Linking a GitLab project that lived under a subgroup failed with a generic "Failed to fetch metadata" error, even when the connected token had full access. The metadata lookup was double-encoding the project path before sending it to GitLab.

  • Fixed GitLab project lookups for any multi-segment path (e.g. group/subgroup/project)
  • Linking repositories deep in nested GitLab groups now succeeds on the first try
  • Branch listing, commit history, file content, and tree fetches across nested GitLab projects also resolve correctly

Try these features today