From 51b7dbfe50b1bd22ba4e74c5597e8dc5d0ba2a56 Mon Sep 17 00:00:00 2001 From: Matt McLoughlin Date: Wed, 21 Apr 2021 12:24:34 -0700 Subject: [PATCH] Update 2.3.0 release notes (#218) --- README.md | 6 +++--- docs/release-notes/2.3.0.md | 3 ++- 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 10f16e1e..fda973b2 100644 --- a/README.md +++ b/README.md @@ -1,9 +1,9 @@ # Welcome to Cromwell on Azure ### Latest release - * [Release 2.2.1](https://github.com/microsoft/CromwellOnAzure/releases/tag/2.2.1)
- [Release notes for version 2.2.1](docs/release-notes/2.2.1.md) + * [Release 2.3.0](https://github.com/microsoft/CromwellOnAzure/releases/tag/2.3.0)
+ [Release notes for version 2.3.0](docs/release-notes/2.3.0.md) -Check the "Update Instructions" section in the version 2.2.1 [release notes](docs/release-notes/2.2.1.md/#update-instructions) to learn how to update an existing Cromwell on Azure deployment to version 2.2.1. You can customize some parameters when updating. Please [see these customization instructions](docs/troubleshooting-guide.md/#Customize-your-Cromwell-on-Azure-deployment), specifically the "Used by update" and "Comment" columns in the table.
+Check the "Update Instructions" section in the version 2.3.0 [release notes](docs/release-notes/2.3.0.md/#update-instructions) to learn how to update an existing Cromwell on Azure deployment to version 2.3.0. You can customize some parameters when updating. Please [see these customization instructions](docs/troubleshooting-guide.md/#Customize-your-Cromwell-on-Azure-deployment), specifically the "Used by update" and "Comment" columns in the table.
#### Getting started * What is [Cromwell on Azure?](#Cromwell-on-Azure)
diff --git a/docs/release-notes/2.3.0.md b/docs/release-notes/2.3.0.md index e5fe075e..69f7d428 100644 --- a/docs/release-notes/2.3.0.md +++ b/docs/release-notes/2.3.0.md @@ -2,7 +2,8 @@ ## Bug fixes and enhancements 1. Disabled binary logging in MySQL to conserve disk space on the data disk ([#205](https://github.com/microsoft/CromwellOnAzure/issues/205)) -2. Fixed the logic that determines the top WorkflowId from TES Task properties. This only affects users who are directly querying CosmosDB and are using the WorkflowId field in a predicate ([#209](https://github.com/microsoft/CromwellOnAzure/issues/209)). +2. Fixed the logic that determines the top WorkflowId from TES Task properties. This only affects users who are directly querying CosmosDB and are using the WorkflowId field in a predicate ([#209](https://github.com/microsoft/CromwellOnAzure/issues/209)). +3. Occassionally the deployer would hang due to the VM not rebooting. Changed deployer reboot logic to use the OS-level command instead of the Azure RM command ([#217](https://github.com/microsoft/CromwellOnAzure/issues/217)). ## Update instructions