Blueprint Studio v2.4.1 — Release Notes
Release date: 2026-03-20
Please read release notes for v2.4.0 for major additions and improvements.
This is a patch release fixing four bugs — three across the Git and Gitea changes panels, and one in the YAML validator.
Bug Fixes
Git panel file staging now works correctly
Selecting files via checkbox in the Git changes panel and clicking Stage was showing a "No files selected" warning even when files were visually checked.
Green push arrow button now triggers a push (Git and Gitea)
After staging and committing, the green arrow_upward button (showing commits ahead of remote) and orange arrow_downward button (showing commits behind) appeared in both panel headers but did nothing when clicked.
Validator no longer false-errors on automation files using blueprints
Validating an automations.yaml that contained use_blueprint: entries produced a false "Blueprint must be a YAML mapping (dict)" error toast, even though the file was perfectly valid.
Root cause: The file-type detector used a plain substring check ('blueprint:' in content). Because use_blueprint: contains the substring blueprint:, automation files were misclassified as blueprint files and sent to the blueprint validator. Blueprint files must be a YAML dict, but automation files are a YAML list, so the validator immediately rejected them.
What changed: The detection now uses a regex ((?:^|\n)blueprint\s*:) that only matches blueprint: as a standalone key at the start of a line. use_blueprint: no longer triggers the blueprint validator.
Full Changelog: v2.4.0...v2.4.1