Repository navigation
Tags: CSharpClub/durabletask
Tags
Fix compatibility issue between older clients and newer workers on DT… ….AzureStorage (Azure#651)
fixed DeleteAllDataForOrchestrationInstance method to return rowsDele… …ted (Azure#635)
Incremented AzureStorage to 1.9.3 (Azure#612)
Set up build signing pipeline with Azure Pipelines (Azure#606) Also: * Created solution just for building DurableTask.AzureStorage and DurableTask.Core * Removed legacy static analysis, which was only working for net461 anyways * Updated some test projects from .net core 2.1 (out of support) to .net core 3.1
Prepare DurableTask.Core and DurableTask.AzureStorage release (Azure#582 ) The previous fix Azure#560 was not actually released as the fix is contained in DurableTask.Core, which was not released as a part of DurableTask.AzureStorage v1.8.8. The fix in Azure#560 is more severe than we thought as it makes a TaskHubWorker lose an entire partition when it completes an orchestration, so we are also releasing a new version of DurableTask.AzureStorage that depends on DurableTask.Core having this fix.
Prepare DurableTask.Core and DurableTask.AzureStorage release (Azure#582 ) The previous fix Azure#560 was not actually released as the fix is contained in DurableTask.Core, which was not released as a part of DurableTask.AzureStorage v1.8.8. The fix in Azure#560 is more severe than we thought as it makes a TaskHubWorker lose an entire partition when it completes an orchestration, so we are also releasing a new version of DurableTask.AzureStorage that depends on DurableTask.Core having this fix.
PreviousNext