v2.0.5

Added

• Added support for Python 3.12.

v2.0.4

Fixed

• Fixed bug introduced in 2.0.3 that only affected the Slurm backend.
• Fixed the behavior of the cancel command (can now cancel multiple target, even if cancelling one of them fails).

v2.0.3

Fixed

• Fixed path validation when using named paths (thanks, Anders!)

Changed

• Updated list of known Slurm states in Slurm backend.

v2.0.2

Added

• You can now filter by "failed" status in the status command (thanks Ludvig).
• The output of gwf status -f summary is now more consistent, has colors,
  and shows all possible states instead of only non-zero ones (thanks, Jakob Grove).

Fixed

• Fixed bug where a failed target would not be included as dependency when
  submitting an upstream target.
• When accounting is enabled in the Slurm backend (on by default), gwf will
  now requests job states from both squeue and sacct, with the status
  from squeue taking precedence. This prevents strange-looking output from gwf status when a target has been submitted, but its state has not yet been
  flushed to the database by Slurm.

v2.0.1

Added

• You can now specify which parts of a workflow to touch with the gwf touch command.
  E.g. gwf touch Foo will only touch Foo and its dependencies (and their dependencies).

Fixed

• Fixed loading of entrypoints on Python 3.7.

v2.0.0

This is a major release. Many internals have been changed, specifically on the scheduler,
which is now much more robust and consistent, and to backends, which now can report whether
a target failed or not. The local backend has also been rewritten from scratch. In the
future it will be able to support e.g. target cancellation.

Added

• For supported backends (currently slurm and local), the status command can now show
  failed targets. These will be rescheduled as if they were incomplete. If accounting is
  not enabled in slurm, this functionality must be turned off with
  gwf config set backend.slurm.accounting_enabled no.

Fixed

• The configuration directory will now always be placed next to the workflow file in use.
• The status command is now consistent with the output of gwf runn.
• The scheduler will not re-run targets that are not "should run".
• Targets with only outputs will now be scheduled if an output file is missing. Otherwise,
  it will not be scheduled.
• And many, many other tiny things!

Changed

• Workflows can no longer be included into each other. All namespacing has been removed.
• Templates returning tuples are no longer supported. Templates must now return an AnonymousTarget.
• APIs for loading workflow, using the scheduler, creating and loading backends etc. have
  been changed. This only affects plugins and custom backends.
• The gwf init command has been removed. Instead, gwf will ask if a skeleton should be
  created in the current directory, if it can't find an existing workflow file.
• Spec hashing is now turned off by default since it can be confusing. It can be turned on
  with gwf config set use_spec_hashes yes.

v1.8.5

Added

• Spec hashes will now be computed automatically on the first run with spec
  hashes enabled.
• gwf touch will now also update spec hashes.