Unreleased
No builder-facing changes yet.3.19.0.dev4 - 2026-08-12
Breaking Changes
- #6401: Ordered-block steps now
reject unknown YAML properties. The removed collect-step keys
force_collectionandtool:are no longer accepted — useask_before_filling: trueinstead. The agent also fails to start when a skill directory cannot be parsed or when two skill directories in the sameskills/tree declare the same skill id.
Improvements
- #6428: Maestro projects without an
endpoints.ymlno longer log errors about the missing file when running CLI commands such asrasa train. Endpoint-backed tracing, metrics, and secrets configuration is skipped instead. CALM projects are unaffected. - #6423: Tools can read
another skill’s
publicmemory (andproject.*) via fully-qualified names oncontext.memory.get, with the same visibility as conditions /read_all(private fields anddeny_readstill blocked). Writes stay scoped to the active skill and project. - #6401: Step and skill load
validation now surfaces clearer, actionable error messages (including migration
hints for the removed collect-step keys), and
rasa data validatereports unloadable skill directories instead of relying on silent skips at runtime. - #6405: Langfuse tracing is configured under optional
tracing:inintegrations.yml(type: langfuse,${VAR}keys, optional knobs such asenvironmentandtimeout). Example agents no longer rely onendpoints.ymlfor tracing; Langfuse declared only inendpoints.ymlstill works with a deprecation warning until you migrate the block.
Documentation
- #6423: The
tools and memory.yml references
document fully-qualified
context.memory.getreads for sibling public fields. - #6401: The
skill.md reference documents ordered-block step
validation, the removed-key migration table, and collect-step authoring without
per-step
tool:overrides.