🗑️ This dev branch should be deleted after merging to main.
:brain: Aim, Context and Functionality
upgrade the PHB version to 2.1.0 ahead of the release
:hammer_and_wrench: Impacted Workflows/Tasks & Changes Being Made
This will affect the behavior of the workflow(s) even if users don’t change any workflow inputs relative to the last version : Yes
Running this workflow on different occasions could result in different results, e.g. due to use of a live database, "latest" docker image, or stochastic data processing : No
:clipboard: Workflow/Task Step Changes
🔄 Data Processing
Docker/software or software versions changed: task_versioning.wdl upgraded to output PHB v2.1.0
Databases or database versions changed: N/A
Data processing/commands changed: N/A
File processing changed: N/A
Compute resources changed: N/A
➡️ Inputs
N/A
⬅️ Outputs
All PHB workflows will now output PHB v2.1.0
:test_tube: Testing
Test Dataset
Doesn't matter, just need to test on at least one workflow
Commandline Testing with MiniWDL or Cromwell (optional)
Test any workflow that runs the task_versioning.wdl task, which is almost everything
Theiagen Version Release Testing (optional)
Will changes require functional or validation testing (checking outputs etc) during the release? functional
Do new samples need to be added to validation datasets? If so, upload these to the appropriate validation workspace Google bucket (). Please describe the new samples here and why these have been chosen. No
Are there any output files that should be checked after running the version release testing? No
:microscope: Final Developer Checklist
[x] The workflow/task has been tested locally and results, including file contents, are as anticipated
[x] The workflow/task has been tested on Terra and results, including file contents, are as anticipated
[x] The CI/CD has been adjusted and tests are passing (to be completed by Theiagen developer)
This PR closes #513
🗑️ This dev branch should be deleted after merging to main.
:brain: Aim, Context and Functionality
upgrade the PHB version to 2.1.0 ahead of the release
:hammer_and_wrench: Impacted Workflows/Tasks & Changes Being Made
This will affect the behavior of the workflow(s) even if users don’t change any workflow inputs relative to the last version : Yes
Running this workflow on different occasions could result in different results, e.g. due to use of a live database, "latest" docker image, or stochastic data processing : No
:clipboard: Workflow/Task Step Changes
🔄 Data Processing
Docker/software or software versions changed:
task_versioning.wdl
upgraded to outputPHB v2.1.0
Databases or database versions changed: N/A
Data processing/commands changed: N/A
File processing changed: N/A
Compute resources changed: N/A
➡️ Inputs
N/A
⬅️ Outputs
All PHB workflows will now output
PHB v2.1.0
:test_tube: Testing
Test Dataset
Doesn't matter, just need to test on at least one workflow
Commandline Testing with MiniWDL or Cromwell (optional)
skipped
Terra Testing
Testing w theiacov_fasta: https://app.terra.bio/#workspaces/theiagen-validations/curtis-sandbox-theiagen-validations/job_history/c5986459-6e09-4c2c-949e-120f893f1c55
⚠️ need to review version output✅ version output is updated as expected
Suggested Scenarios for Reviewer to Test
Test any workflow that runs the task_versioning.wdl task, which is almost everything
Theiagen Version Release Testing (optional)
:microscope: Final Developer Checklist
🎯 Reviewer Checklist
🗂️ Associated Documentation (to be completed by Theiagen developer)