Skip to content

Commit

Permalink
pin cwltool==3.1.20241217163858 (relates to common-workflow-language/…
Browse files Browse the repository at this point in the history
  • Loading branch information
fmigneault committed Dec 18, 2024
1 parent 31e0969 commit 63aee8f
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 2 deletions.
6 changes: 6 additions & 0 deletions CHANGES.rst
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,12 @@ Changes:
case-by-case details about the specific cause of failure handled by the *rule* callable.
- Update certain ``cornice`` service definitions that were using "``prov``" as referencing to `Providers` to avoid
confusion with the multiple ``PROV``/`Provenance` related terminology and services added for the new feature.
- Pin ``cwltool==3.1.20241217163858`` to employ the official release including
``PROV`` configuration provided to easily configured `Weaver`
(relates to `common-workflow-language/cwltool#2082 <https://github.com/common-workflow-language/cwltool/pull/2082>_)
and integrate previously provided fixes
(relates to `common-workflow-language/cwltool#2082 <https://github.com/common-workflow-language/cwltool/pull/2036>_)
that were applied by a forked backport ``https://github.com/fmigneault/cwltool`` repository.

Fixes:
------
Expand Down
3 changes: 1 addition & 2 deletions requirements.txt
Original file line number Diff line number Diff line change
Expand Up @@ -42,8 +42,7 @@ cryptography
# use cwltool gpu-enabled support until integrated within the original tool
# (https://github.com/common-workflow-language/common-workflow-language/issues/587)
### git+https://github.com/crim-ca/cwltool@docker-gpu#egg=cwltool
##cwltool==3.1.20230906142556
cwltool @ git+https://github.com/fmigneault/cwltool.git@cwl-prov-class
cwltool==3.1.20241217163858
# for some reason, not the same release number,
# but same code as https://github.com/common-workflow-language/cwlprov/tree/0.6.0
cwlprov==0.1.1
Expand Down

0 comments on commit 63aee8f

Please sign in to comment.