May 13, 2026 · @lava
We reduced the default lifetime of user keys from one week to 15 minutes. Sessions transparently refresh, so this is invisible in normal use, but shortens the window in which a leaked key could be reused.
]]>May 13, 2026 · @mavam, @codex · #47
Project fixtures can now declare Python package dependencies inline with PEP 723 metadata:
# /// script
# dependencies = ["boto3"]
# ///
tenzir-test installs these dependencies with uv before importing fixture
modules, so fixtures used during regular test runs and tenzir-test --fixture
can manage their own Python package requirements.
Select tests by requested fixture name with the new --fixture-name option:
tenzir-test --fixture-name node
tenzir-test tests/alerts --match kafka --fixture-name docker-compose
--fixture-name can be repeated and combines with --fixture-tag using OR
semantics before intersecting with positional test paths and --match.
Fixture selectors are long-only; the previous -F alias for --fixture-tag
has been removed before the CLI shape settles.
May 12, 2026 · @mavam, @codex · #44
tenzir-test now requires Python 3.13 or newer.
Users on Python 3.12 need to upgrade their interpreter before installing or running the CLI:
uvx --python 3.13 tenzir-test --help
The Tenzir skill collection is now published as its initial stable release for v1.0.0.
This release establishes the shared skill set as the stable baseline for coding agents working in and around the Tenzir ecosystem.
]]>May 11, 2026 · @mavam, @codex · #42
Select tests by fixture tag with the new --fixture-tag option:
tenzir-test --fixture-tag container
tenzir-test --fixture-tag docker-compose
Fixture tags are cumulative and can be repeated. The selector intersects with positional test paths and --match patterns, so you can narrow a directory to container-backed tests or run only tests that request the built-in Docker Compose fixture.
Fixtures that use the shared container runtime helpers inherit the container tag automatically. Custom fixtures can pass explicit tags at registration time when they use their own abstraction.
May 9, 2026 · @mavam, @codex · #41
The test harness can detect the installed Tenzir version across current and upcoming Tenzir releases. This keeps startup/version checks working during the transition to the next Tenzir release series.
]]>May 6, 2026 · @gitryder
The Stream view now includes a timeline that shows event volume over time, segmented by schema. It automatically detects timestamp fields and adapts its bucket size to the data’s time range, providing an at-a-glance view of when events occur and which schemas are most active.
It also probes your data for time fields and shows availability inline, omitting events without a recognized time field (ts, timestamp, or time).
May 5, 2026 · @gitryder
You can now navigate between entries in the Explorer table using arrow keys. Press Space to toggle the inspector, then use Arrow Up and Arrow Down to move between rows and seamlessly across pages.
Apr 21, 2026 · @gitryder
We moved field selection in the Explorer's table view into a dedicated popover. The 'Fields' button sits in the toolbar and shows how many fields are currently hidden. Opening it reveals the full field list with the same click-to-toggle and shift+click-to-focus behavior as before.
]]>May 5, 2026 · @mavam, @codex · #40
Hook diagnostics emitted with --debug now use the same formatting as the rest of the harness debug trace. Previously, hook invocation messages used ad-hoc debug: lines, which made debug output inconsistent.
May 4, 2026 · @mavam, @codex · #23
The validate command now reports unknown changelog entry metadata keys instead of silently accepting them. This catches misspelled fields such as co-authors early, before they are ignored by release workflows.
Apr 29, 2026 · @mavam, @codex · #39
Suite-level requires.operators checks now apply consistently to every test runner. Mixed suites that combine TQL, shell, Python, or custom tests no longer depend on the first runner type to decide whether required Tenzir operators are available.
Apr 29, 2026 · @mavam, @codex · #38
Suite-scoped fixture setup and teardown failures now appear as regular test failures instead of aborting the entire run with a Python traceback.
This lets the harness continue with independent queued tests after a fixture assertion or cleanup error.
]]>Apr 27, 2026 · @mavam, @codex · #36
Projects can now register Python hooks that run at stable tenzir-test lifecycle points, including before settings discovery:
from tenzir_test import hooks
@hooks.startup
def use_local_build(ctx):
ctx.path.insert(0, str(ctx.root / "build" / "bin"))
ctx.env["TENZIR_BINARY"] = str(ctx.root / "build" / "bin" / "tenzir")
ctx.env["TENZIR_NODE_BINARY"] = str(ctx.root / "build" / "bin" / "tenzir-node")
This makes it possible to select local Tenzir binaries, prepare project-scoped environment variables, and collect diagnostics for failed tests without wrapping the test command in custom shell scripts. Use --no-hooks or TENZIR_TEST_DISABLE_HOOKS=1 to bypass hooks when debugging.
Apr 22, 2026 · @mavam, @codex · #35
The test harness now honors skip: {on: fixture-unavailable} for fixtures that are selected by individual tests:
skip:
on: fixture-unavailable
fixtures:
- optional-service
This lets parameterized per-test fixtures skip only the tests that need the unavailable service. Suite fixtures still require the opt-in in directory-level test.yaml, so one test's frontmatter cannot control the whole suite.
Apr 21, 2026 · @lava, @gitryder
Workspace management has been enhanced with new capabilities for administrators. You can now rename workspaces directly from the workspace settings, and the Users tab now provides a unified interface for managing workspace access. Administrators can view all users with access to a workspace in a single table and easily change user roles between member and admin roles using dropdown controls.
Apr 21, 2026 · @lava, @gitryder
The Tenzir Platform now supports organizations, giving teams a shared home for collaborating across workspaces. Organization admins can invite members, assign admin or member roles, and manage which workspaces belong to the organization. Members get access to all workspaces owned by the organization and can leave from their user settings at any time.
Learn more in the organization management guide.
]]>100% passed and 0% failed.
The final aggregate summary now reports non-perfect pass and fail percentages whenever at least one executed test fails. Previously, rounding could show 100% passed and 0% failed for runs with a small number of failures, even though the overall result was not a full success.
For example, a run like 586 passed / 1 failed / 152 skipped now renders the executed-test percentages as 99% passed and 1% failed. This makes mixed outcomes easier to spot at a glance in the CLI output.
The reusable release workflow no longer emits the Node 20 deprecation warning when it generates GitHub App tokens on GitHub-hosted runners.
Repositories that call tenzir/ship/.github/workflows/release.yaml now get clean release logs without extra configuration.
v-prefixed tags. It keeps release publishing, local development, and CI installs on maintained versions without changing normal tenzir-ship usage.
The repository's locked Python dependencies now use patched upstream releases, including fixes for the open security advisories reported by Dependabot.
This refresh keeps local development and CI installs on maintained versions without changing normal tenzir-ship usage.
The release publish --commit workflow now uses the tag-form version in generated release commits and annotated tag messages.
For example, publishing v1.1.0 now creates Release v1.1.0 instead of Release 1.1.0:
tenzir-ship release publish v1.1.0 --commit --tag --yes
This keeps generated release commits aligned with the corresponding Git tag and avoids mismatches in automation that expects the v-prefixed release identifier.
Apr 7, 2026 · @gitryder
We added thousands separators to numeric values in the pipeline Insights tab, making large numbers easier to read at a glance.
Apr 7, 2026 · @gitryder
We fixed an issue where the pipeline table stayed filtered after viewing a pipeline's detail page and navigating away to another tab. Returning to the Pipelines page would show only the previously viewed pipeline, and clearing the search had no effect.
]]>The reusable GitHub Actions release workflow now works in external repositories by default. It falls back to the caller repository's GITHUB_TOKEN, makes GitHub App authentication optional, and only enables GPG signing when a caller provides a signing key and opts into commit and/or tag signing. The single release.yaml workflow now also exposes the advanced hooks and release controls directly, including skip-publish for dry runs and smoke tests. Tenzir repositories can still opt into the existing bot identity, GitHub App token flow, and signed commits and tags by passing those settings explicitly.
Mar 27, 2026 · @gitryder
You can now choose which fields are visible in the Explorer's table view. When you select a schema in the sidebar, its fields are listed below. Click a field to hide its column from the table. Shift+click a field to show only that field. A "fields hidden" indicator in the table header lets you clear all hidden fields at once. Field selections are remembered per schema and reset when you run a new pipeline.
Mar 26, 2026 · @gitryder
You can now filter events in the Stream view by clicking schemas in the sidebar. The schemas panel shows color-coded dots matching each schema's badge color, and selecting one or more schemas limits the view to only those events. Same-name schema variants are merged into a single entry in the sidebar for easier navigation.
Mar 26, 2026 · @gitryder
We added a new Stream view to the Explorer that shows all pipeline results as a continuous list of expandable events. You can switch between the Table, Chart, and Stream views using the view selector in the toolbar. The Stream view displays events from all schemas together, with color-coded badges to distinguish between them. Each row shows a one-line preview that you can expand to inspect the full event. The view remembers your selection across pipeline runs, and the event list scrolls horizontally as a whole, with schema badges staying pinned on the left.
Mar 13, 2026 · @gitryder
You can now sort the Explorer table by clicking column headers. Sortable columns show a sort indicator, and clicking cycles through ascending, descending, and unsorted states. Sorting works for both top-level and nested fields.
Mar 12, 2026 · @gitryder
You can now click on field names and values in the Explorer inspector to copy them to the clipboard. Field names copy the full dot-separated path, and values copy their TQL representation.
Mar 12, 2026 · @gitryder
You can now select a time range directly from the Explorer header. Choose from quick presets like 5 minutes or 12 hours, or open the custom popover to pick from a grid of relative durations or set an absolute date range. The selector is currently available for pipelines that start with the export operator.
Mar 12, 2026 · @gitryder
We combined the 'About' and 'Install' tabs in the package detail drawer into a single scrollable view. Package information, examples, and configuration options are now shown on one page instead of requiring tab switches.
Mar 24, 2026 · @gitryder
We fixed an issue where custom packages installed on a node were not visible in the library view. Previously, only packages from the official Tenzir library were shown. Custom packages are now included alongside library packages.
Mar 24, 2026 · @gitryder
We fixed a bug where operator description text on the package detail page appeared rotated 90 degrees, overlapping other content.
Mar 17, 2026 · @gitryder
Packages containing user-defined operators can again be installed through the platform. Previously, installing such packages failed because the operator arguments were serialized incorrectly. This only affected installs through the platform UI—command-line package installs were not impacted.
]]>Mar 20, 2026 · @mavam, @codex · #20
This fixes the release candidate workflow so RCs no longer remain in changelog history after they have been superseded. Creating a new -rc.N now replaces the previous RC for that cycle, and creating a stable release closes the RC cycle and removes its RC manifests from releases/.
For example:
# Start an RC cycle for a later stable release.
tenzir-ship release create v1.2.3 --rc --yes
tenzir-ship release create v1.3.0 --yes
# Or promote the active RC to its matching stable release.
tenzir-ship release create v1.2.3 --rc --yes
tenzir-ship release create --yes
After the stable release is created, the RC is no longer kept in release history. Release candidates are also cumulative, so each new RC includes the previous RC's entries plus any newly added unreleased entries, while stable releases remain incremental.
]]>tenzir-ship now supports release candidates via release create --rc. Creating a release candidate snapshots the current unreleased entries without consuming them, so you can iterate on -rc.N releases before promoting one to the final stable release. The stable base is inferred automatically, and rerunning the command continues the matching RC series when one already exists.
When you are ready to ship the stable release, rerun tenzir-ship release create without --rc and the latest outstanding release candidate becomes the matching stable release automatically. Once an RC series exists, you either continue it with release create --rc or promote the latest candidate with the normal stable command.
Publishing a release candidate now automatically creates a GitHub prerelease and prevents it from being marked as latest. release version and show latest continue to resolve the latest stable release, while release publish without an explicit version now targets the latest release manifest, including RCs. The bundled GitHub Actions release workflows accept rc so you can keep creating RCs from CI, and the default stable workflow promotes the latest outstanding candidate automatically.
Mar 12, 2026 · @lava
We upgraded Python dependencies and added system-level package upgrades to the Docker images to address known vulnerabilities.
Mar 11, 2026 · @realllydan
We fixed an issue where switching away from a pipeline that has the Insights tab available to one that does not could leave the tab selection in an invalid state.
]]>The bundled GitHub Actions workflows now use Node 24-compatible action versions, which keeps CI, release, and publishing automation aligned with GitHub's runtime transition. The release and sync workflows also mint GitHub App installation tokens without relying on a deprecated JavaScript action.
Release commands and the Python API now handle release versions more consistently when changelog data mixes tag-style versions such as v1.2.3 with bare semantic versions such as 1.2.3. This improves compatibility with existing changelog histories and makes release automation more reliable across commands that inspect, create, show, and publish releases.
Skipping a test no longer modifies its baseline file. Previously, running
with --update would overwrite the baseline of a skipped test with an empty
file, and running without --update would fail if the baseline was non-empty.
Skipped tests now leave existing baselines untouched, so toggling a skip
condition no longer causes unrelated baseline churn.
init command scaffolds changelog projects interactively or non-interactively, so you can set up a standalone or package-based project in less time. It also protects existing projects from accidental overwrites.
A new init command allows for scaffolding a new changelog project interactively or with the --yes flag. It supports both standalone and package modes, and prevents accidental overwriting of existing projects.
tenzir-ship init
This reduces the manual effort required to set up a new changelog.
]]>Mar 10, 2026 · @lava
The app container now supports a PRIVATE_WEBSOCKET_GATEWAY_ENDPOINT environment variable that overrides the existing PUBLIC_WEBSOCKET_GATEWAY_ENDPOINT for calls in the app backend. This allows configuring different endpoints when the frontend and backend live in different networks.
Mar 10, 2026 · @realllydan
The pipeline detail modal now includes an experimental Insights tab that visualizes per-operator backpressure, helping users identify bottlenecks in their pipelines. This tab is only available for pipelines running on the experimental new executor.
Mar 10, 2026 · @lava
We fixed an issue where ephemeral nodes were causing the frontend to fail to render or be displayed with incorrect connection status.
]]>Mar 5, 2026 · @lava
When you click a deep link in Tenzir Platform but aren't logged in, you're now redirected to your original destination after signing in, instead of landing on the home page.
Feb 18, 2026 · @gitryder
We improved how the nodes list loads, making dependent views feel faster and more responsive across the platform.
Feb 27, 2026 · @gitryder
We fixed an issue where profile images from Gravatar and Microsoft accounts were blocked by the content security policy, causing broken or missing avatars.
Feb 27, 2026 · @gitryder
We fixed an issue where the diagnostics pane could show diagnostics from a different pipeline than the one currently open in the detail modal.
Feb 18, 2026 · @gitryder
We fixed an issue where the context list could appear in a random order when no search was active, causing items to jump around. The list now uses a stable alphabetical order so it stays consistent and easier to interact with.
Feb 18, 2026 · @gitryder
We fixed an issue where opening a pipeline link for a workspace you don’t have access to would log you out. You are now redirected to the access page where you can open the link in your default workspace.
]]>Mar 4, 2026 · @mavam, @claude, @codex
We improved clarity and efficacy of the releasing process in the tenzir-ship agent skill.
Mar 1, 2026 · @mavam, @claude, @codex · #11
The pi-tenzir-ship package provides a skill for AI coding agents to perform
release engineering tasks. Install it in Pi with:
pi install npm:pi-tenzir-ship
Then activate it with /skill:tenzir-ship.
The skill covers adding changelog entries, cutting standard and module releases, triggering GitHub Actions release workflows, and publishing releases to GitHub.
Feb 28, 2026 · @mavam, @codex · #10
The release creation command now automatically updates version fields in package manifest files during release. When creating a release, tenzir-ship detects and updates package.json, pyproject.toml, project.toml, and Cargo.toml files in your project, including support for dynamic version files in monorepo workspaces.
You can control this behavior with the release.version_bump_mode configuration option in your config.yaml:
auto (default): Automatically detect and update version filesoff: Skip version file updatesFor more granular control, use the release.version_files option to explicitly specify which files to update. Auto-detection searches the project root and parent directory (for nested changelog projects) and gracefully skips files without static version fields.
Release version selection now defaults to automatic bumping when you run
release create without an explicit version and without --patch, --minor,
or --major. The next version is inferred from unreleased entry types:
If no unreleased changelog entries exist, automatic bumping is not available. In that case, provide an explicit version or a manual bump flag to create an intro-only release.
The stats command now reports the computed next release version (or no value
when no automatic bump can be inferred), including in stats --json.
Feb 28, 2026 · @mavam, @codex · #9
Create releases with only introductory text and no changelog entries by using the --intro or --intro-file flags with release create. This is useful when re-publishing a package after yanking a previous artifact or retrying a failed publish workflow—scenarios where you want to create a new release version without adding changelog entries.
Previously, you had to provide at least one changelog entry to create a release. Now the release creation allows you to skip the entries entirely if you supply intro text. The --intro flag accepts text directly, while --intro-file reads from a Markdown file.
reusable-release.yaml now acts as a minimal opinionated wrapper around a new
reusable-release-advanced.yaml workflow.
The advanced workflow adds optional hooks and release controls for complex
consumers: pre/post publish scripts, non-main --no-latest publishing,
optional copy of release directories to main, latest branch updates, a
skip-publish dry-run mode, and workflow outputs for version and
is_latest.
Release commands now validate changelog directory structure before they run and fail fast when it is invalid.
release create and release publish now stop with explicit errors when stray files or directories are detected (for example, an unexpected changelog/next/ directory). Other commands (show, add, stats, and release version) emit warnings so layout problems are visible earlier, while validate reports full structural issues as regular validation errors.
Feb 15, 2026 · @mavam, @claude · #7
When a release step fails, the full command now prints below the progress panel so you can copy-paste it for manual recovery.
Previously, long commands would get truncated in the release progress panel, making it difficult to reproduce the failure manually. Now when a step fails, the complete command is displayed in full below the panel, giving you what you need to debug and retry the operation.
]]>Parallel suites are now scheduled more reliably when running with --jobs > 1, so interdependent tests (for example publisher/subscriber pairs) start together sooner instead of being delayed behind large backlogs of unrelated tests.
This update also adds an explicit correctness guard for parallel suites: you can set suite.min_jobs in test.yaml to declare the minimum job count required for valid execution. The run now fails fast if --jobs is lower than suite.min_jobs, and it also fails hard when a parallel suite cannot reserve at least min_jobs workers at runtime (for example under slot contention), instead of proceeding under-provisioned.
In addition, the harness now warns when a parallel suite has more tests than available jobs, making it easier to spot cases where effective suite parallelism is capped by worker count.
]]>Feb 25, 2026 · @mavam, @codex · #32
Python fixture tests could fail with serialization errors when the test
configuration included enum values like mode: sequential in test.yaml.
These values are now properly converted to strings before being passed to
test scripts.
Feb 24, 2026 · @mavam, @codex · #29
Test suites can now execute their members in parallel by specifying mode: parallel in the suite configuration. By default, suites continue to run tests sequentially for stability and predictability.
To enable parallel execution, set mode: parallel in the test.yaml file alongside the suite configuration:
suite:
name: my-suite
mode: parallel
fixtures:
- node
Parallel suite execution is useful when tests within a suite are independent and can safely run concurrently. All suite members share the same fixtures and execute within the same fixture lifecycle, while test execution itself happens on separate threads. The suite thread pool is bounded by --jobs, so suite-level concurrency stays within the configured worker budget and does not scale unbounded with suite size.
Suite-level constraints like timeouts, fixture requirements, and capability checks still apply uniformly across all members, whether running sequentially or in parallel.
Feb 25, 2026 · @mavam, @codex · #31
Interrupting test runs with Ctrl+C now exits cleanly without leaking Python tracebacks from subprocess or fixture startup/teardown paths. Interrupt-shaped errors (including nested causes with signal-style return codes such as 130) are treated as graceful cancellation so the CLI reports interrupted tests instead of crashing.
Feb 24, 2026 · @mavam, @codex · #30
Shell test files (.sh) now always default to the "shell" runner, even when a directory-level test.yaml file specifies a different runner (for example, runner: tenzir). This makes shell scripts work reliably in mixed-runner directories without requiring explicit runner: frontmatter in each file. Explicit runner: declarations in test file frontmatter still take precedence and can override this behavior if needed.
Manual fixture control now behaves consistently for fixtures that declare dataclass options.
Previously, starting a fixture with acquire_fixture(...) could fail when no
explicit options were provided, even if the fixture defined defaults.
With this fix, current_options(...) returns default typed options in the
manual fixture-control path, so fixtures started manually and fixtures started
through normal test activation behave the same way.
Feb 18, 2026 · @gitryder
We improved the clarity and usability of Explorer charts. Legends are now collapsible, easier to read, and support filtering series directly. Pie chart legends adapt better to available space, and tooltips provide clearer information.
We also expanded the chart color palette for better visual distinction between series, fixed bar chart x-axis labels overlapping when there are many data points, and refined chart layout and behavior for a smoother overall experience.
Feb 18, 2026 · @gitryder
Resolved an issue where your Google profile picture did not appear in the workspace switcher. The image now loads and displays correctly.
Feb 17, 2026 · @lava
Fixed a bug where the static workspace synchronization used stale loop variables during cleanup, causing stale workspaces to persist and the last configured workspace to be incorrectly deleted.
Feb 17, 2026 · @gitryder
We fixed an issue where pressing ESC to close a pipeline detail view caused the pipeline list to stop responding to clicks.
]]>Feb 22, 2026 · @mavam, @codex · #28
Test suites can now declare operator dependencies with a requires configuration key in test.yaml. When a required operator is unavailable in the target Tenzir build, you can gracefully skip the suite by pairing requires with skip: {on: capability-unavailable}.
The skip.on key now accepts either a single condition as a string or a list of conditions, letting you skip on either fixture-unavailable or capability-unavailable (or both). When a capability is unavailable and the suite doesn't opt into skipping, the test run fails with a clear error message listing the missing operators.
Example configuration in test.yaml:
requires:
operators: [from_gcs, to_s3]
skip:
on: capability-unavailable
reason: requires from_gcs and to_s3 operators
This ensures test suites targeting specific capabilities only run when those capabilities are present, improving test reliability in heterogeneous build environments.
]]>Feb 18, 2026 · @mavam, @codex · #27
Fixtures can now define assertion hooks that run after test execution completes while fixtures remain active. Define assertions using the assertions parameter with a frozen dataclass type, then pass fixture-specific assertion payloads under assertions.fixtures.<name> in test frontmatter. The framework automatically invokes the assert_test hook with assertion data before tearing down fixtures, letting you validate side effects like HTTP requests or log output.
Example usage with an HTTP fixture:
fixtures: [http]
assertions:
fixtures:
http:
count: 1
method: POST
path: /api/endpoint
body: '{"key":"value"}'
The HTTP fixture receives the typed assertion payload and validates that the expected request was received. Payload structure is fixture-defined, so fixtures can choose flat fields or nested schemas as needed.
Assertion checks are tracked separately from test counts in the run summary as pass/fail check metrics, so fixture-level validations are visible without changing total test counts.
]]>Feb 17, 2026 · @gitryder
We updated the Platform's underlying framework dependencies to include their latest security fixes.
]]>Feb 16, 2026 · @mavam, @codex · #26
The test harness no longer initializes fixtures for suites where all tests are statically skipped. Previously, fixtures were activated even when no tests would run, causing unnecessary startup overhead and potential errors.
Feb 16, 2026 · @mavam, @codex · #25
When a fixture becomes unavailable during test execution, the test harness now provides a clean error message instead of a Python traceback.
]]>Feb 15, 2026 · @mavam, @codex · #23, #24
tenzir-test now supports both coarse and fine-grained controls for running skipped tests.
Use --run-skipped as a sledgehammer, or --run-skipped-reason with the same matching semantics as --match (bare substring or glob):
tenzir-test --run-skipped
tenzir-test --run-skipped-reason 'maintenance'
tenzir-test --run-skipped-reason '*docker*'
If both options are provided, --run-skipped takes precedence.
Feb 15, 2026 · @mavam, @codex · #22
Writing container-based fixtures no longer requires duplicating boilerplate for runtime detection, process management, and readiness polling.
The new container_runtime module provides reusable building blocks that handle
the common plumbing: detecting whether Docker or Podman is available, launching
containers in detached mode, polling for service readiness, and tearing down
cleanly. Custom fixtures can import these helpers and focus on their
service-specific logic instead.
The built-in docker-compose fixture and the example project now use these
shared helpers internally.
Adds a built-in docker-compose fixture that starts and tears down Docker Compose services from structured fixture options.
The fixture validates Docker Compose availability, waits for service readiness (health-check first, running-state fallback), and exports deterministic service environment variables (including host-published ports).
Feb 14, 2026 · @mavam, @claude · #20
You can now start fixtures in foreground mode without running any tests by using the --fixture option. This lets you provision services (like a database or message broker) and use them in your workflow.
Specify fixture names or YAML-style configuration:
uvx tenzir-test --fixture mysql
uvx tenzir-test --fixture 'kafka: {port: 9092}' --debug
The harness prints fixture-provided environment variables like HOST, PORT, and DATABASE, then keeps services running until you press Ctrl+C. You can repeat --fixture to activate multiple fixtures. The option is mutually exclusive with positional TEST arguments.
Feb 13, 2026 · @mavam, @claude · #19
Configuration override log messages now use relative paths and human-friendly formatting instead of absolute paths and raw Python repr output, making debug output easier to read.
]]>Feb 11, 2026 · @mavam, @claude · #18
Fixture options now support nested dataclass hierarchies, allowing you to structure complex configurations with multiple levels of organization.
Previously, fixture options were limited to flat fields. Now you can declare nested dataclasses as field types, and tests can pass deeply structured options through frontmatter:
fixtures:
- node:
server:
message:
greeting: world
Type safety is preserved across all nesting levels. Optional nested fields (declared with Optional[T] or T | None) are supported, and omitted nested records use their default values. The example server fixture demonstrates this capability with a message.greeting field that flows through to environment variables.
Feb 10, 2026 · @lava
We upgraded pnpm to 9.15.0 in the frontend Docker image to address CVE-2024-53866.
]]>Feb 10, 2026 · @mavam, @claude · #17
Fixtures can now receive typed configuration options passed from test YAML files.
Declare options on a fixture with @fixture(options=MyDataclass), where MyDataclass is a frozen dataclass. Tests can then provide structured options in their frontmatter using either compact syntax (for simple cases) or expanded syntax (for clarity):
fixtures:
- node:
tls: true
port: 8443
- http:
port: 9090
The @fixture decorator validates that option keys match the dataclass fields, and the fixture retrieves its typed instance using current_options(name). When options aren't provided, fixtures receive a default-constructed instance of their options class.
The feature maintains backward compatibility with the existing fixtures: [node, http] syntax for fixtures without options.
You can now click on the Ingress or Egress legend item to isolate that series in the activity chart. Clicking again shows both series, making it easier to analyze each metric when lines overlap.
Feb 6, 2026 · @gitryder
We added a toggle in the Explorer table Inspector that lets you wrap lines for easier reading.
We now display the current platform version at the bottom of the workspace switcher dropdown,️ making it easier to always see which version you’re on.
Jan 28, 2026 · @gitryder · #38
We added sorting for the Live Activity column in the pipelines table, so you can easily order pipelines by their activity level.
Jan 28, 2026 · @gitryder · #29
We unified the Available and Installed library tabs into a single view, so you can see which packages are installed without switching tabs. You can also uninstall packages directly from the same page.
Feb 9, 2026 · @lava
We fixed a bug in the Inspector where strings containing backslashes were not displayed correctly. Backslashes were not being escaped in TQL string rendering. For example, a string like Hello \World\ was previously rendered as "Hello \World\" instead of "Hello \\World\\". The fix ensures backslashes are properly escaped when displayed.
skip
configurations in test.yaml failed with a JSON serialization error.
Python fixture tests that use skip in their test.yaml no longer fail with
Object of type SkipConfig is not JSON serializable.