fix(lambda): bump the aws-powertools group in /lambdas with 4 updates

[dependabot]

Bumps the aws-powertools group in /lambdas with 4 updates: @aws-lambda-powertools/parameters, @aws-lambda-powertools/logger, @aws-lambda-powertools/metrics and @aws-lambda-powertools/tracer.

Updates @aws-lambda-powertools/parameters from 2.22.0 to 2.23.0

Release notes

Sourced from @​aws-lambda-powertools/parameters's releases.

v2.23.0

Summary

We're excited to announce a new resolver for AppSync GraphQL APIs in the Event Handler utility. It simplifies routing and processing of events in AWS Lambda functions by allowing you to define resolvers for specific GraphQL types and fields.

We’ve also fixed two bugs in Logger: 1/ one causing timestamps to be incorrectly formatted when using non-UTC timezone and around midnight, and 2/ another causing temporary keys to not be properly cleared when using the injectLambdaContext() Middy.js middleware.

Finally, starting from this release we're publishing our Lambda layers in the AWS China Beijing Region operated by Sinnet.

🌟 A huge thank you to @​arnabrahman for the amazing work on the AppSync GraphQL resolver 🎉

Working AppSync GraphQL APIs

Key Features

• Route events based on GraphQL type and field keys
• Automatically parse API arguments to function parameters
• Handle GraphQL responses and errors in the expected format

To get started install the Event Handler utility by running:

npm install @aws-lambda-powertools/event-handler

Registering a resolver

Docs

You can register functions to match GraphQL types and fields with one of three methods:

• onQuery() - Register a function to handle a GraphQL Query type.
• onMutation() - Register a function to handle a GraphQL Mutation type.
• resolver() - Register a function to handle a GraphQL type and field.

Your resolvers receive the parsed arguments from the GraphQL request as their first parameter. We will take care of parsing the response or catching errors and returning them in the expected format.

You can register a resolver for a Query type, you can use the onQuery() method. This method allows you to define a function that will be invoked when a GraphQL Query is made.

import { AppSyncGraphQLResolver } from '@aws-lambda-powertools/event-handler/appsync-graphql';
import { Logger } from '@aws-lambda-powertools/logger';
import type { Context } from 'aws-lambda';
const logger = new Logger({
serviceName: 'TodoManager',
});
const app = new AppSyncGraphQLResolver({ logger });
app.onQuery<{ id: string }>('getTodo', async ({ id }) => {
</tr></table>

... (truncated)

Changelog

Sourced from @​aws-lambda-powertools/parameters's changelog.

2.23.0 (2025-07-02)

Bug Fixes

• ci: Partition workflows (#4084) (40195dd)
• logger: reset keys on error in middleware (#4122) (e310c50)
• logger: set hourCycle to h23 when tz is not UTC (#4102) (54b0863)

Features

• event-handler: add single resolver functionality for AppSync GraphQL API (#3999) (b91383f)
• event-handler: expose event & context as object (#4113) (7e74c9e)
• event-handler: support onQuery and onMutation handlers (#4111) (263db2d)

Commits

• b8e6d93 chore(ci): bump version to 2.23.0 (#4123)
• e310c50 fix(logger): reset keys on error in middleware (#4122)
• 7c3196f docs(event-handler): add AppSync GraphQL docs page (#4120)
• 7e74c9e feat(event-handler): expose event & context as object (#4113)
• 263db2d feat(event-handler): support onQuery and onMutation handlers (#4111)
• dfc31da chore(deps): bump @​types/node from 24.0.7 to 24.0.8 (#4107)
• 5d783ee chore(deps): bump the aws-sdk-v3 group across 1 directory with 9 updates (#4106)
• 3359dbe chore(deps): bump mkdocs-material from 9.6.14 to 9.6.15 in /docs (#4104)
• 94a690e chore(deps): bump squidfunk/mkdocs-material from eb04b60 to 0bfdba4 in /d...
• f6374e1 chore(deps): bump the aws-cdk group across 1 directory with 2 updates (#4108)
• Additional commits viewable in compare view

Updates @aws-lambda-powertools/logger from 2.22.0 to 2.23.0

Release notes

Sourced from @​aws-lambda-powertools/logger's releases.

v2.23.0

Summary

We're excited to announce a new resolver for AppSync GraphQL APIs in the Event Handler utility. It simplifies routing and processing of events in AWS Lambda functions by allowing you to define resolvers for specific GraphQL types and fields.

We’ve also fixed two bugs in Logger: 1/ one causing timestamps to be incorrectly formatted when using non-UTC timezone and around midnight, and 2/ another causing temporary keys to not be properly cleared when using the injectLambdaContext() Middy.js middleware.

Finally, starting from this release we're publishing our Lambda layers in the AWS China Beijing Region operated by Sinnet.

🌟 A huge thank you to @​arnabrahman for the amazing work on the AppSync GraphQL resolver 🎉

Working AppSync GraphQL APIs

Key Features

• Route events based on GraphQL type and field keys
• Automatically parse API arguments to function parameters
• Handle GraphQL responses and errors in the expected format

To get started install the Event Handler utility by running:

npm install @aws-lambda-powertools/event-handler

Registering a resolver

Docs

You can register functions to match GraphQL types and fields with one of three methods:

• onQuery() - Register a function to handle a GraphQL Query type.
• onMutation() - Register a function to handle a GraphQL Mutation type.
• resolver() - Register a function to handle a GraphQL type and field.

Your resolvers receive the parsed arguments from the GraphQL request as their first parameter. We will take care of parsing the response or catching errors and returning them in the expected format.

You can register a resolver for a Query type, you can use the onQuery() method. This method allows you to define a function that will be invoked when a GraphQL Query is made.

import { AppSyncGraphQLResolver } from '@aws-lambda-powertools/event-handler/appsync-graphql';
import { Logger } from '@aws-lambda-powertools/logger';
import type { Context } from 'aws-lambda';
const logger = new Logger({
serviceName: 'TodoManager',
});
const app = new AppSyncGraphQLResolver({ logger });
app.onQuery<{ id: string }>('getTodo', async ({ id }) => {
</tr></table>

... (truncated)

Changelog

Sourced from @​aws-lambda-powertools/logger's changelog.

2.23.0 (2025-07-02)

Bug Fixes

• ci: Partition workflows (#4084) (40195dd)
• logger: reset keys on error in middleware (#4122) (e310c50)
• logger: set hourCycle to h23 when tz is not UTC (#4102) (54b0863)

Features

• event-handler: add single resolver functionality for AppSync GraphQL API (#3999) (b91383f)
• event-handler: expose event & context as object (#4113) (7e74c9e)
• event-handler: support onQuery and onMutation handlers (#4111) (263db2d)

Commits

• b8e6d93 chore(ci): bump version to 2.23.0 (#4123)
• e310c50 fix(logger): reset keys on error in middleware (#4122)
• 7c3196f docs(event-handler): add AppSync GraphQL docs page (#4120)
• 7e74c9e feat(event-handler): expose event & context as object (#4113)
• 263db2d feat(event-handler): support onQuery and onMutation handlers (#4111)
• dfc31da chore(deps): bump @​types/node from 24.0.7 to 24.0.8 (#4107)
• 5d783ee chore(deps): bump the aws-sdk-v3 group across 1 directory with 9 updates (#4106)
• 3359dbe chore(deps): bump mkdocs-material from 9.6.14 to 9.6.15 in /docs (#4104)
• 94a690e chore(deps): bump squidfunk/mkdocs-material from eb04b60 to 0bfdba4 in /d...
• f6374e1 chore(deps): bump the aws-cdk group across 1 directory with 2 updates (#4108)
• Additional commits viewable in compare view

Updates @aws-lambda-powertools/metrics from 2.22.0 to 2.23.0

Release notes

Sourced from @​aws-lambda-powertools/metrics's releases.

v2.23.0

Summary

We're excited to announce a new resolver for AppSync GraphQL APIs in the Event Handler utility. It simplifies routing and processing of events in AWS Lambda functions by allowing you to define resolvers for specific GraphQL types and fields.

We’ve also fixed two bugs in Logger: 1/ one causing timestamps to be incorrectly formatted when using non-UTC timezone and around midnight, and 2/ another causing temporary keys to not be properly cleared when using the injectLambdaContext() Middy.js middleware.

Finally, starting from this release we're publishing our Lambda layers in the AWS China Beijing Region operated by Sinnet.

🌟 A huge thank you to @​arnabrahman for the amazing work on the AppSync GraphQL resolver 🎉

Working AppSync GraphQL APIs

Key Features

• Route events based on GraphQL type and field keys
• Automatically parse API arguments to function parameters
• Handle GraphQL responses and errors in the expected format

To get started install the Event Handler utility by running:

npm install @aws-lambda-powertools/event-handler

Registering a resolver

Docs

You can register functions to match GraphQL types and fields with one of three methods:

• onQuery() - Register a function to handle a GraphQL Query type.
• onMutation() - Register a function to handle a GraphQL Mutation type.
• resolver() - Register a function to handle a GraphQL type and field.

Your resolvers receive the parsed arguments from the GraphQL request as their first parameter. We will take care of parsing the response or catching errors and returning them in the expected format.

You can register a resolver for a Query type, you can use the onQuery() method. This method allows you to define a function that will be invoked when a GraphQL Query is made.

import { AppSyncGraphQLResolver } from '@aws-lambda-powertools/event-handler/appsync-graphql';
import { Logger } from '@aws-lambda-powertools/logger';
import type { Context } from 'aws-lambda';
const logger = new Logger({
serviceName: 'TodoManager',
});
const app = new AppSyncGraphQLResolver({ logger });
app.onQuery<{ id: string }>('getTodo', async ({ id }) => {
</tr></table>

... (truncated)

Changelog

Sourced from @​aws-lambda-powertools/metrics's changelog.

2.23.0 (2025-07-02)

Bug Fixes

• ci: Partition workflows (#4084) (40195dd)
• logger: reset keys on error in middleware (#4122) (e310c50)
• logger: set hourCycle to h23 when tz is not UTC (#4102) (54b0863)

Features

• event-handler: add single resolver functionality for AppSync GraphQL API (#3999) (b91383f)
• event-handler: expose event & context as object (#4113) (7e74c9e)
• event-handler: support onQuery and onMutation handlers (#4111) (263db2d)

Commits

• b8e6d93 chore(ci): bump version to 2.23.0 (#4123)
• e310c50 fix(logger): reset keys on error in middleware (#4122)
• 7c3196f docs(event-handler): add AppSync GraphQL docs page (#4120)
• 7e74c9e feat(event-handler): expose event & context as object (#4113)
• 263db2d feat(event-handler): support onQuery and onMutation handlers (#4111)
• dfc31da chore(deps): bump @​types/node from 24.0.7 to 24.0.8 (#4107)
• 5d783ee chore(deps): bump the aws-sdk-v3 group across 1 directory with 9 updates (#4106)
• 3359dbe chore(deps): bump mkdocs-material from 9.6.14 to 9.6.15 in /docs (#4104)
• 94a690e chore(deps): bump squidfunk/mkdocs-material from eb04b60 to 0bfdba4 in /d...
• f6374e1 chore(deps): bump the aws-cdk group across 1 directory with 2 updates (#4108)
• Additional commits viewable in compare view

Updates @aws-lambda-powertools/tracer from 2.22.0 to 2.23.0

Release notes

Sourced from @​aws-lambda-powertools/tracer's releases.

v2.23.0

Summary

We're excited to announce a new resolver for AppSync GraphQL APIs in the Event Handler utility. It simplifies routing and processing of events in AWS Lambda functions by allowing you to define resolvers for specific GraphQL types and fields.

We’ve also fixed two bugs in Logger: 1/ one causing timestamps to be incorrectly formatted when using non-UTC timezone and around midnight, and 2/ another causing temporary keys to not be properly cleared when using the injectLambdaContext() Middy.js middleware.

Finally, starting from this release we're publishing our Lambda layers in the AWS China Beijing Region operated by Sinnet.

🌟 A huge thank you to @​arnabrahman for the amazing work on the AppSync GraphQL resolver 🎉

Working AppSync GraphQL APIs

Key Features

• Route events based on GraphQL type and field keys
• Automatically parse API arguments to function parameters
• Handle GraphQL responses and errors in the expected format

To get started install the Event Handler utility by running:

npm install @aws-lambda-powertools/event-handler

Registering a resolver

Docs

You can register functions to match GraphQL types and fields with one of three methods:

• onQuery() - Register a function to handle a GraphQL Query type.
• onMutation() - Register a function to handle a GraphQL Mutation type.
• resolver() - Register a function to handle a GraphQL type and field.

Your resolvers receive the parsed arguments from the GraphQL request as their first parameter. We will take care of parsing the response or catching errors and returning them in the expected format.

You can register a resolver for a Query type, you can use the onQuery() method. This method allows you to define a function that will be invoked when a GraphQL Query is made.

import { AppSyncGraphQLResolver } from '@aws-lambda-powertools/event-handler/appsync-graphql';
import { Logger } from '@aws-lambda-powertools/logger';
import type { Context } from 'aws-lambda';
const logger = new Logger({
serviceName: 'TodoManager',
});
const app = new AppSyncGraphQLResolver({ logger });
app.onQuery<{ id: string }>('getTodo', async ({ id }) => {
</tr></table>

... (truncated)

Changelog

Sourced from @​aws-lambda-powertools/tracer's changelog.

2.23.0 (2025-07-02)

Bug Fixes

• ci: Partition workflows (#4084) (40195dd)
• logger: reset keys on error in middleware (#4122) (e310c50)
• logger: set hourCycle to h23 when tz is not UTC (#4102) (54b0863)

Features

• event-handler: add single resolver functionality for AppSync GraphQL API (#3999) (b91383f)
• event-handler: expose event & context as object (#4113) (7e74c9e)
• event-handler: support onQuery and onMutation handlers (#4111) (263db2d)

Commits

• b8e6d93 chore(ci): bump version to 2.23.0 (#4123)
• e310c50 fix(logger): reset keys on error in middleware (#4122)
• 7c3196f docs(event-handler): add AppSync GraphQL docs page (#4120)
• 7e74c9e feat(event-handler): expose event & context as object (#4113)
• 263db2d feat(event-handler): support onQuery and onMutation handlers (#4111)
• dfc31da chore(deps): bump @​types/node from 24.0.7 to 24.0.8 (#4107)
• 5d783ee chore(deps): bump the aws-sdk-v3 group across 1 directory with 9 updates (#4106)
• 3359dbe chore(deps): bump mkdocs-material from 9.6.14 to 9.6.15 in /docs (#4104)
• 94a690e chore(deps): bump squidfunk/mkdocs-material from eb04b60 to 0bfdba4 in /d...
• f6374e1 chore(deps): bump the aws-cdk group across 1 directory with 2 updates (#4108)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions