v0.9.0

🔧 Updates to Experiments

Adding breakpoints to components in a Pipeline

It's now possible to set breakpoints at any component in any pipeline, forcing the pipeline execution to stop before that component runs and generating a JSON file with the complete state of the pipeline before the breakpoint component was run.

Usage Examples

# Setting breakpoints
pipeline.run(
    data={"input": "value"},
    breakpoints={("component_name", 0)},  # Break at the first visit
    debug_path="debug_states/"
)

This will generate a JSON with the complete pipeline state before the next component is run, i.e.: the one receiving the output of the component set in the breakpoint

# Resuming from a saved state
state = Pipeline.load_state("debug_states/component_state.json")
pipeline.run(
    data={"input": "value"},
    resume_state=state
)

🧑‍🍳 See an example notebook here
💬 Share your feedback in this discussion

✅ Adopted Experiments

• chore: Remove Agent after Haystack 2.12 release (#263) @julian-risch
• chore: Remove AutoMergingRetriever after Haystack 2.12 release (#265) @davidsbatista

Other Updates

• Proposal for changing internal working of Agent (#245) @sjrl
• refactor: Streamline super components input and output mapping logic (#243) @sjrl
• refactor: Small updates to Agent. Make pipeline internal, add check for warm_up (#244) @sjrl
• feat: Updates to insertion of values into State (#239) @sjrl
• feat: Add unclassified to output of MultiFileConverter (#240) @julian-risch
• feat: Enhance tool error logs and some refactoring (#235) @sjrl

Full Changelog: v0.8.0...v0.9.0