0.13.0

• Improvements:
  • Added support for build-level metadata (#138). See Build Metadata for details
  • UI support for some kinds of metadata:
    • :human-readable-build-label
  • Added events :pipeline-started and :pipeline-finished (#155)
  • Added function to simplify handling of nested step-results (e.g. the information received from :pipeline-finished events (#155, #154):
    • lambdacd.steps.result/flatten-step-result-outputs
  • Added functions to simplify getting information about a specific step (#154):
    • lambdacd.presentation.pipeline-structure/flatten-pipeline-representation
    • lambdacd.presentation.pipeline-structure/step-display-representation-by-step-id
• Bug fixes:
  • Catch Exception instead of Throwable in build steps to avoid catching Errors which cannot be handled (#148), thanks @hgsy!
• Deprecated:
  • lambdacd.execution was deprecated in favor of lambdacd.execution.core
• Breaking Changes:
  • Removed :unify-status-fn parameter in execute-steps (deprecated since 0.9.4). Use :unify-results-fn instead. lambdacd.steps.support/unify-only-status can help with migrating unify-status-fns.
• Changes in internal API:
  • lambdacd.internal.execution was refactored into several independent namespaces, functions were moved around, replaced or made private.
    You shouldn't have dependencies on those unless you are doing something really crazy or advanced. If you did, please consider using functions in public namespaces (i.e. that don't have internal in their name).
    If you have dependencies on functions that have no public equivalent, please open an issue to get this fixed.