Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Upgrade Current Version to 1.1
See original GitHub issueNow that 1.1 is live, we should update the documentation to point to 1.1 as the current version
Issue Analytics
- State:
- Created 2 years ago
- Comments:11 (7 by maintainers)
Top Results From Across the Web
Update to enable TLS 1.1 and TLS 1.2 as default secure ...
Describes an update that adds TLS 1.1 and TLS 1.2 to default security protocols in Windows Server 2012, Windows 7 SP1, and Windows...
Read more >Upgrading from Version 7.1.1.1 or earlier on WebSphere ... - IBM
Upgrading from Version 7.1.1.1 or earlier on WebSphere Application Server · Click Applications > Application types. · Click WebSphere enterprise applications.
Read more >Upgrade firmware 1.1.x to current version via series of two SD ...
Upgrade firmware 1.1.x to current version via series of two SD cards-X ; Insert the second SD-card ; Plug in the power cord...
Read more >Upgrading to Newer Releases — Flask Documentation (1.1.x)
This section of the documentation enumerates all the changes in Flask from release to release and how you can change your code to...
Read more >Upgrading from versions 1.1.3 and older
Go to Advanced Options > Update Checker, click the Upload binary image button, select the upgrade image file, wait until the file is...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
A great way to demonstrate to the community that WDL != Cromwell would be to not hold up advancing the current version of the spec to 1.1 just because Cromwell does not yet support it.
Answering your original question - yes, wdlTools supports 1.1.
I am going to remove the
blockedlabel. Anyone please feel free to re-apply it if you really think it’s justified to hold this up until all runtimes support 1.1.