Releases: Azure/azure-functions-powershell-worker
Releases · Azure/azure-functions-powershell-worker
v3.0.226 Release of PowerShell worker for Azure Functions (PowerShell 7)
This PowerShell Worker version is to be used with Azure Functions v3 only.
The changes for this release are:
- Migrated to PowerShell 7.0.0-rc.2.
- Directory structure changed to enable installing PowerShell 6 and 7 workers side-by-side.
- Use Get-Error instead of custom error formatting logic (#395).
v3.0.216 Release of PowerShell worker for Azure Functions
This PowerShell Worker version is to be used with Azure Functions v3 only.
The changes for this release are:
- Upgraded to PowerShell 6.2.4.
- Minor internal improvements.
v2.0.215 Release of PowerShell worker for Azure Functions
This PowerShell Worker version is to be used with Azure Functions v2 only.
The changes for this release are:
- Upgraded to PowerShell 6.2.4.
- Minor internal improvements.
v1.0.201 Release of PowerShell worker for Azure Functions
The changes for this release are:
- Minor internal improvements.
v1.0.197 Release of PowerShell worker for Azure Functions
The major changes for this release are:
- Added experimental support for the Function Chaining pattern (Durable Functions).
Please note: this implementation is incomplete, has known limitations, and the programming model will change soon, so avoid enabling Durable PowerShell Functions in production!
v1.0.194 Release of PowerShell worker for Azure Functions
The major changes for this release are:
- Resolved an issue that was sometimes making automatically installed modules intermittently unavailable until the first app reboot (issue #351).
- Improved system log messages related to dependency management.
v1.0.188 Release of PowerShell worker for Azure Functions
The major changes for this release are:
- The blob size limit for PowerShell functions triggered by blob is determined by the Functions host now, which effectively raised the limit from 4 MB to 120 MB (fixed issue #346).
- Introduced TraceContext parameter (see issue Azure/azure-functions-host#3747).
- Improved system log messages.
v0.1.174 Release of PowerShell worker for Azure Functions
The major changes for this release are:
- Upgraded to PowerShell 6.2.3.
- Breaking change: HTTP request body is not automatically deserialized from JSON unless the request contains
application/json
in theContent-Type
header, or there is noContent-Type
header (fixed issue #241). - Management Dependencies upgrade forces PowerShell worker restarts when new module versions are detected.
- Improved error and exception logging for function code.
- Added a warning when a function invocation is blocked because of concurrency limit.
- Other logging improvements.
v0.1.159 Release of PowerShell worker for Azure Functions
The major changes for this release are:
- Fixed cold start time regression when using Managed Dependencies.
- Fixed a problem with installing some modules from the PowerShell Gallery when using the
<MajorVersion>.*
pattern.
v0.1.152 Release of PowerShell worker for Azure Functions
The major changes for this release are:
- Major Managed Dependencies update:
- Allowed specifying any (not just
Az
) module from PowerShell Gallery inrequirements.psd1
(up to 10 entries). - Allowed specifying exact module versions in
requirements.psd1
(as opposed to just<MajorVersion>.*
pattern), including pre-release versions. - More reliable implementation of module upgrades (fixing #247, #248, #252, and other intermittent issues).
- Improved cold start performance.
- Added a warning when
managedDependencies
is enabled inhost.json
but no dependencies are specified inrequirements.psd1
.
- Allowed specifying any (not just
- Fixed issue #281 (Clear pushed output binding values on exceptions).
- System logging fixes and improvements.