You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 26601c8
Browse filesBrowse the repository at this point in the historyBrowse files
fix: revert pre-fork hooks for multi-concurrent mode
This reverts commit fa006b6 (#226).
The pre-fork hooks change introduced in 4.1.0 is breaking, so it is
removed: the `awslambdaric.lambda_concurrency_hooks` module, the
`@register_pre_fork` decorator and the `Runtime.PreForkError` error
type are gone, restoring the 4.0.4 multi-concurrent startup flow. The
on-demand path is unaffected.
Bumps the version to 4.2.1 and adds a release note.
Copy file name to clipboardExpand all lines: RELEASE.CHANGELOG.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,7 @@
1
+
### October 13, 2026
2
+
`4.2.1`
3
+
- Revert pre-fork hooks for multi-concurrent (Lambda Managed Instances) mode introduced in `4.1.0` ([#226](https://github.com/aws/aws-lambda-python-runtime-interface-client/pull/226)), as the change was breaking. The `awslambdaric.lambda_concurrency_hooks` module, the `@register_pre_fork` decorator and the `Runtime.PreForkError` error type are removed, restoring the `4.0.4` multi-concurrent startup behavior. No impact on the standard on-demand path.
4
+
1
5
### October 7, 2026
2
6
`4.2.0`
3
7
- Add a `w3c()` helper to `LambdaContext` that returns the W3C trace-context fields (`traceparent`, `tracestate`, `baggage`) carried on `clientContext.w3c` at invoke time ([#228](https://github.com/aws/aws-lambda-python-runtime-interface-client/pull/228))
0 commit comments