Skip to content

Conversation

@vsmalladi
Copy link
Collaborator

@vsmalladi vsmalladi commented Dec 19, 2025

Closes #25

@vsmalladi vsmalladi requested a review from claymcleod December 19, 2025 15:17
Updated the announcement date and improved clarity on various aspects of WDL 1.2.1, including file semantics, path resolution, function clarifications, example fixes, and testing infrastructure.
@vsmalladi vsmalladi requested a review from patmagee January 10, 2026 18:53
This release includes clarifications, deprecations, bug fixes to examples, and improvements to the testing infrastructure:

* **File and Directory Semantics**:
* Clarify `File` and `Directory` path canonicalization, validation, and equality semantics. Clarify when `File`s and `Directories` must exist (at declaration evaluation time, not access time). Add `Directory` comparison operators to binary operators table.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be nice to link to the PRs that introduced these behaviors. You can see a full list of the PRs and issues here: https://github.com/openwdl/wdl/milestone/6?closed=1

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep good idea.


* **Path Resolution and Deprecations**:
* Clarified that relative paths in `File` and `Directory` declarations are resolved relative to the WDL document's parent directory outside the `output` section, and relative to the task's execution directory inside the `output` section. Also clarified that optional files evaluate to `None` in both contexts if the path does not exist.
* Deprecated the use of relative path literals in input and private variable declarations.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this conflicts with the item above where we clarified how relative paths behave (how could we deprecate it and also clarify its use?)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ya i need to remove this. We had removed it in an eralier PR and I didn't get rectify the conflict.

* **Example Fixes**:
* Included fixes to examples introduced in v1.1.3.
* Fixed issues with examples that don't compile in wdl-tests thanks to [@adamnovak](https://github.com/adamnovak), [@stxue1](https://github.com/stxue1), [@claymcleod](https://github.com/claymcleod) and [@vsmalladi](https://github.com/vsmalladi):
* HISAT2 example uses unsupported `--sra-acc` option - fixed by updating to valid options.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here: if we have removed these examples, then these items about fixing HISAT2 and GATK are meaningless and should be removed too.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed. Artifact of doing this too early.

categories: wdl bioinformatics workflows
---

# Announcing WDL 1.2.1
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would link to the appropriate milestone in both blog posts.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea.

@claymcleod
Copy link
Contributor

Personally, I prefer more prose-like blog posts categorizing all of the changes, explaining why they were made, and explaining what they mean to the user. Otherwise, they just read like a CHANGELOG.md, which we already have in the repository. My advice is, if you don't want to go through making a prose blog post, just make a single-paragraph blog posts that points out some of the high-level features and then links to the CHANGELOG.md.

@vsmalladi
Copy link
Collaborator Author

Ya I will make it more blog posty. I wanted to make sure content was mostly truthful and accurate since it has been a while since I wrote some of this and lots of things have been in flight. Will update this and 1.1.3 as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

New blog post for 1.2.1

3 participants