v0.12.0: Important bugfix. Minor API change.

This release contains an important bugfix, making sure that we properly handle all errors (#146).

It also contains a minor API change, that could affect custom components making use of the AtomizeIPs() method, which is now renamed to FinalizePaths().

v0.11.2-rc4: Properly handle errors when finalizing paths

This release fixes a bug where some errors were not properly handled and reported on finalizing paths.

v0.11.2-rc3: Fix wrong error message in concatenator component

This Release Candidate fixes an erroneous error message in the concatenator component, that might result in confusion when debugging.

v0.11.2-rc2: Fix behavior in globber

This release fixes a behavior in the globber component, making sure that it waits for all its dependencies to arrive before globbing.

v0.11.2-rc1: Try to fix #143: Fix problem with creating directories in concatenator

Try to fix #143: Fix problem with creating directories in concatenator

This is a pre-release, release candidate.

v0.11.1: Fix error about potential TempDir clashes

This is a small bugfix release, fixing bug #142 about a potential collision between TempDir paths.

v0.11.0: Better logging

This is a rather small release, which fixes issue #134 and improves logging, by making sure that more context information, such as process, task, workflow or file-IP name is included wherever applicable.

It increases more than the most minor part in the version since it contains some smaller breaking changes, in particular that the NewFileIP() constructor returns errors instead of failing the program locally (this is, as you might have guessed, part of the move towards logging errors in a place with more context available).

v0.10.2: Enhancement: Properly fail if not all ports are closed at the same time in IPSelectorSync

This is a small release fixing issue #135.

v0.10.1: Fix #131: Don't panic on erroneous path trimming

• Fixes #131

v0.10.0: Bugfix: Basename modifier should not include parent dir part

This release fixes bug #130. Read more in the bug description for info about this. We are bumping to 0.10.0 as this is potentially a breaking change for workflows already using the basename modifier.