v0.3.0 v4.7.1
low risk
roboflow/supervisionOct 2, 2026 → Oct 2, 20260 days between releases
What's New
Shift from MLX/Laya runtime fixes to Trigger.dev CLI init fixes and auth visibility.
Breaking Changes
- Criteria keys that were previously silently ignored are now rejected in v0.3.0.
New Features
- Added `answer_confidence` field in v0.3.0.
- CLI and MCP authorization pages now show specific accounts and organizations in v4.7.1.
Improvements
- Improved conversation truncation to preserve newest turns in v0.3.0.
- Enhanced language detection and email cleaning for multilingual routing in v0.3.0.
- CLI init now provides clear errors for missing package.json in v4.7.1.
- Task directories are now correctly written to trigger.config.ts during init.
Bug Fixes
- Fixed zero-room left-truncation edge case in v0.3.0.
- Fixed prompt-prefix LRU protection under concurrent preparation in v0.3.0.
- Fixed init command installing packages into parent project instead of target directory in v4.7.1.
The Two Releases
v0.3.0
laya-mlx v0.3.0
Oct 2, 2026· 20 days ago
The native MLX port selectively incorporates upstream Laya runtime fixes, focusing on conversation truncation, custom labels, and Unicode preservation.
Full release notesv4.7.1
trigger.dev v4.7.1
Oct 2, 2026· 20 days ago
A patch release fixing the `trigger.dev init` command to handle missing `package.json` correctly and improving visibility of authorization pages.
Full release notes