Skip to content

Release 2026-05-15 #2382

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
GarrettBeatty merged 2 commits into from
May 15, 2026
Merged

Release 2026-05-15 #2382

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c688f0e
release_2026-05-15
aws-sdk-dotnet-automation May 15, 2026
b18ce7e
Updated changelog
aws-sdk-dotnet-automation May 15, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 0 additions & 19 deletions .autover/changes/apigateway-websocket-aspnetcore.json
View file
Open in desktop

This file was deleted.

8 changes: 8 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,13 @@
## Release 2026-05-15

### Amazon.Lambda.AspNetCoreServer (10.1.0)
* Add APIGatewayWebsocketApiProxyFunction (and TStartup variant) so API Gateway WebSocket APIs can be hosted via LambdaServer (DI, controllers). WebSocket events are dispatched as POST requests whose path is the RouteKey, allowing controller actions like [HttpPost("$default")] to handle them.
* Expose ParseHttpPath, ParseHttpMethod, and AddMissingRequestHeaders as protected virtual hooks on APIGatewayProxyFunction so subclasses can customize how the API Gateway request is mapped onto the ASP.NET Core request feature.
### Amazon.Lambda.AspNetCoreServer.Hosting (2.1.0)
* Add LambdaEventSource.WebsocketApi so AddAWSLambdaHosting can wire ASP.NET Core minimal APIs and controllers up to API Gateway WebSocket events.

## Release 2026-05-15

### AWSLambdaPSCore PowerShell Module (5.0.1)
* Fix dotnet10 runtime failures by updating template package references to versions with net10.0 assets. Bumped Amazon.Lambda.PowerShellHost from 3.0.3 to 4.0.0, Amazon.Lambda.Core from 2.8.1 to 3.0.0 (required transitively by PowerShellHost 4.0.0), and the default Microsoft.PowerShell.SDK from 7.5.4 to 7.6.0.

Expand Down
2 changes: 1 addition & 1 deletion .../src/Amazon.Lambda.AspNetCoreServer.Hosting/Amazon.Lambda.AspNetCoreServer.Hosting.csproj
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@
<TargetFrameworks>$(DefaultPackageTargets)</TargetFrameworks>
<ImplicitUsings>enable</ImplicitUsings>
<Nullable>enable</Nullable>
<Version>2.0.0</Version>
<Version>2.1.0</Version>
<PackageReadmeFile>README.md</PackageReadmeFile>
<AssemblyName>Amazon.Lambda.AspNetCoreServer.Hosting</AssemblyName>
<PackageId>Amazon.Lambda.AspNetCoreServer.Hosting</PackageId>
Expand Down
2 changes: 1 addition & 1 deletion Libraries/src/Amazon.Lambda.AspNetCoreServer/Amazon.Lambda.AspNetCoreServer.csproj
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@
<Description>Amazon.Lambda.AspNetCoreServer makes it easy to run ASP.NET Core Web API applications as AWS Lambda functions.</Description>
<TargetFrameworks>$(DefaultPackageTargets)</TargetFrameworks>
<AssemblyTitle>Amazon.Lambda.AspNetCoreServer</AssemblyTitle>
<Version>10.0.0</Version>
<Version>10.1.0</Version>
<AssemblyName>Amazon.Lambda.AspNetCoreServer</AssemblyName>
<PackageId>Amazon.Lambda.AspNetCoreServer</PackageId>
<PackageTags>AWS;Amazon;Lambda;aspnetcore</PackageTags>
Expand Down