0.4.0

• Improvements:
  • Cleaned up status inheritance to make it more consistent
  • Support variable arguments instead of step-vector as input for chain-steps (#29)
  • Internal refactorings to prepare for more component-oriented structure
  • Contexts always contain :step-results-channel which can be used to access a stream of step-state updates,
    e.g. to create custom persistence components or runners (still experimental)
  • Cleaned up dependencies
• Bug fixes:
  • Fix bug in retriggering that left next step in undefined state (#26)
• API changes:
  • Steps returning no :status will now be treated as failures instead of receiving status :undefined
  • Removed deprecated :result-channel argument for execute-step
  • Removed deprecated core/new-base-context-for
  • core/execute-step does no longer output the result-channel data to a :result-channel in ctx.
    Was replaced with :step-results-channels which provides a stream of complete, aggregated step-result data
  • Calling lambdacd.steps.support/chain-steps with a vector instead of just the steps is now deprecated (#29)