Skip to content

Releases: Azure/azure-functions-host

Functions 1.0.11247

14 Sep 23:53
Compare
Choose a tag to compare

Changes in this release:

  • updates to support referencing .NET Standard 2.0 class libraries (#1792)
  • fix for http route constraints containing period (#969)
  • http request binding fix (Azure/azure-webjobs-sdk-extensions#273)
  • updated to Roslyn version 2.3.2
  • updated to F# version 4.4.1
  • cold start optimization work

Functions 1.0.11184

30 Aug 17:51
Compare
Choose a tag to compare

Changes in this release:

  • Moved to App Insights version 2.4
  • Moved to Node.js version 6.11.2
  • CosmosDB trigger updates (new attribute properties/knobs, see Azure/azure-webjobs-sdk-extensions#278)
  • Fixed portal duplicate compilation log issue (#1866)
  • Fixed race condition in Table logging (addresses #1403)
  • Added a dependency on Azure Function Proxies library version 0.3.0.6
  • Miscellaneous other bug fixes

Functions 1.0.11116

16 Aug 18:22
Compare
Choose a tag to compare

Hotfix release containing fixes for the following:

Functions 1.0.11090

14 Aug 17:26
Compare
Choose a tag to compare

Patch release to address issues with Service Bus and Sendgrid bindings.

Functions 1.0.11075

02 Aug 16:45
Compare
Choose a tag to compare

In this release:

Full set of changes here

WebJobs SDK release: https://github.com/Azure/azure-webjobs-sdk/releases/tag/v2.1.0-beta1-10950
Core extensions release: https://github.com/Azure/azure-webjobs-sdk-extensions/releases/tag/v2.1.0-beta1-10467

Functions 1.0.11027

14 Jul 00:42
Compare
Choose a tag to compare

In this release:

  • Miscelaneous bug fixes and improvements
  • Detailed set of changes here

Functions 1.0.11015

21 Jun 23:33
Compare
Choose a tag to compare

In this release:

  • Added new host level configuration knob for EventHubs batchCheckpointFrequency. This setting allows you to control the number of event batches to process before creating an EventHub cursor checkpoint
  • Fixed QueueTrigger bug Azure/azure-webjobs-sdk#1191
  • Additional miscellaneous bug fixes

Functions 1.0.11002

01 Jun 05:54
Compare
Choose a tag to compare

In this release:

  • Support for dotted paths in binding expressions
    • previously binding expressions could only reference the top level binding data properties
    • now, if your trigger data contains nested objects, you can reference those properties as well
    • see Http binding examples below which are a good example of this. However, this works with your own POCO objects as well
  • Http binding support for headers and query parameters
    • you can now reference request header and query string parameter values by name in binding expressions
    • e.g. {headers.MyHeader}, {query.MyParam}
  • Http binding support for nested object properties
    • now, in addition to being able to reference top level properties of JSON bodies, you can reference nested properties as well
    • e.g. assuming JSON payload { a: 123, b: "testing", c: { d: 456 } }, you can use binding expression {c.d} to reference properties of the nested object
  • increased max function timeout from 5 minutes to 10 minutes
    • the default remains the same (5 minutes). You can configure the functionTimeout value as described in the host.json wiki
  • Support for optional string route parameters in Http functions (addresses Azure/azure-webjobs-sdk-extensions#224)
    • e.g. you can now have a route like products/{category:alpha?}/{id:guid?} where the string (alpha) route segement is optional
  • improvements to ServiceBus binding connection management (see Azure/azure-webjobs-sdk#1150)
    • previously for Node.js functions using ServiceBus bindings, we had an issue were we were creating new MessageFactory instances per function invocation. These are now cached/shared as per Service Bus performance guidelines
  • fix for duplicate SQL query parameters in DocumentDB binding (Azure/azure-webjobs-sdk-extensions#228)
  • Added functionDirectory and functionName to the execution context (#1472)
    • e.g. within a Node.js function you can access via context.executionContext.functionDirectory. Within a C# function you'd add an ExecutionContext context parameter and access via context.FunctionName (more details here)
  • various other bug fixes

Functions 1.0.10917

28 Apr 04:08
Compare
Choose a tag to compare

Main things in this release:

  • Application Insights integration (Preview)
  • Native TypeScript support (preview)
  • Improvements to binding extensibility for binding authors
  • JavaScript transpiler API/extension model
  • Miscellaneous bug fixes and improvements

Functions 1.0.10893

17 Apr 20:30
Compare
Choose a tag to compare

Main things in this release:

  • Added support for C# 7.0 (Updated C# compiler - Roslyn)
  • Improvements to Node binding data handling, exposing additional metadata to Node functions (#1346 and additional information here)
  • Implementation of a blob storage backed repository for secrets (#1320)
    • API keys can now be stored in blob storage, decoupling that information from the mounted file system
  • Implementation of HTTP throttling options (#1369)
    • see wiki page here for more info
  • Configurable settings for HTTP queue length, concurrency level, etc. (more details here)
  • Fix to add content-type header to Node request (#1344)
  • Miscellaneous bug fixes and improvements