Releases: cepetr/trezor-bench
Releases · cepetr/trezor-bench
Release list
v0.4.3
This update focuses primarily on internal code maintenance and structural refactoring, alongside resolutions for a few minor bugs.
Changed
- All notification popups now start with a unified
Trezor Bench: - Command-palette entries and Run and Debug entry labels now use the
Trezor Benchprefix instead ofTrezor; the redundant(Trezor)marker was removed from setting descriptions. - Build, Clippy, Check, and Clean start-failure messages now read
<action> failed to start — <error>, matching the Flash and Upload wording.
Fixed
- Build, Flash, and Upload now explain when the active build context is incomplete or no longer matches the manifest, instead of failing silently.
- Flash and Upload are now blocked when manifest availability-rule validation errors block workflow actions.
- Debug-profile variables using obsolete
${tfTools.*}aliases now report a manifest validation error before launch. - Blocked build messages now identify the correct manifest and preset locations to check.
- Build, Clippy, Check, and Clean tasks can now be referenced from
.vscode/tasks.json.
v0.4.2
Changed
- Build-option tooltip descriptions now appear on a new line below the command-line option or multistate value.
- Build artifact rows now show
presentinstead ofvalid, with a consolidatedUpdatedrow showing the newest artifact's relative age.
v0.4.1
Fixed
- Restored the existing repository URL in extension package metadata and README links so the bundled README image resolves correctly.
v0.4.0
Changed
- Renamed the extension from Trezor Firmware Tools to Trezor Bench. This is a breaking change: the extension id is now
cepetr.tbench, and its commands, settings, context keys, debugger and task types, debug variables, persisted workspace state, repository configuration file, and managed IntelliSense directory now use thetbenchprefix. - Retained upstream Trezor firmware contract paths under
xtask/tf-tools/, including the manifest, preset, and debug-template locations.
v0.3.2
Fixed
- Multistate build options without an applicable preset value now use their first declared state, so their state choices remain selectable instead of becoming unavailable.
v0.3.1
- Added root-level
tf-tools.tomlrepository configuration for cargo workspace, manifest, build artifacts, debug templates, and xtask preset input paths. - Removed the
tfTools.cargoWorkspacePath,tfTools.debug.templatesPath,tfTools.artifactsPath, andtfTools.manifestPathVS Code settings. Their values are not migrated; configure repository paths intf-tools.tomlinstead.
v0.3.0
Do not install this release until trezor/trezor-firmware#7389 is merged.
Added
- Added a
Presetselector belowComponentinBuild Selection, listing every preset declared inpresets.tomland the optionaluser-presets.tomlplus a syntheticDefaultchoice. The selected preset id is saved and restored with the rest of the active configuration and never appears in the status bar, task labels, or command names. - Added preset-relative build options: controls display the preset-effective value calculated from shared defaults, user defaults, shared preset fragments, and user preset fragments, and only values explicitly overridden away from that baseline are emphasized. Overrides are discarded for options the newly active preset or build context calculates differently, and retained for those calculated identically.
- Added preset-aware
Build,Clippy, andCheckexecution: the command appends-p <preset-name>only for a non-default preset and emits build-option arguments only for overrides that differ from the preset-effective values. - Added error reporting for preset inputs. A missing
presets.tomlmeans the repository'sxtaskpredates preset support, so the selector reports the file as unavailable; a malformed or invalid preset file replaces the preset choices with an error message. In both cases details go to the log, the saved preset id is preserved, andBuild,Clippy, andCheckare blocked whileCleanstays available. An absentuser-presets.tomlremains optional. - Added persistence of each configuration pane's collapse state across window reloads.
Changed
- Split the single
Configurationtree view into three sibling panes in the activity-bar container —Build Selection,Build Artifacts, andBuild Options, in that order — each with its own header and divider. Row labels, icons, descriptions, tooltips, checkboxes, inline artifact actions, and placeholder wording are unchanged.Build Optionsstarts collapsed. - Moved the workflow toolbar from the container title to the
Build Selectionpane header, keeping its full membership, order, grouping, icons, and enablement. The host reveals pane header actions on hover or focus and hides them while the pane is collapsed;Build OptionsandBuild Artifactsexpose no workflow actions. - Selecting the status bar configuration item now opens the container, expands
Build Selection, and focuses it. - Renamed the activity-bar container from
TrezortoTrezor Firmware Tools. - Multistate build options no longer require manifest-authored defaults; the selected state is inferred from the preset-effective value when no override exists.
v0.2.0
Added
- Added configuration variable expansion for tf-tools path settings, excluded-file scope settings, and task environment settings.
- Added clangd IntelliSense backend support when cpptools is unavailable.
- Added
tfTools.taskExtraEnvfor extra environment variables passed to Build, Clippy, Check, Clean, Flash, and Upload workflow tasks. - Added persistent log output for extension activation and key failure paths, including manifest load failures, blocked Flash/Upload actions, map-file open failures, and debug launch failures.
Changed
- Workflow tasks now launch
cargo xtaskthroughProcessExecution, inheriting the VS Code session environment without shell-mediated startup.
Fixed
- Build artifact status and related actions now refresh after running
cargo xtask buildorcargo xtask cleanoutside the extension.
v0.1.2
v0.1.1
Changelog
0.1.1 - 2026-04-22
Changed
- Lowered the minimum supported VS Code version to 1.105.0