From deb19ecae1034ce5f4b4998696501b9b454b1cd5 Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Wed, 15 May 2024 02:32:50 +0000 Subject: [PATCH] =?UTF-8?q?=E2=AC=86=EF=B8=8F=20Bump=20@aws-lambda-powerto?= =?UTF-8?q?ols/parameters=20from=202.1.0=20to=202.1.1=20(#210)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Bumps [@aws-lambda-powertools/parameters](https://github.com/aws-powertools/powertools-lambda-typescript) from 2.1.0 to 2.1.1.
Release notes

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

v2.1.1

Summary

This patch release brings bug fixes to the Parser and a deprecation notice to the Tracer utility.

Parser

In response to customer reports we have applied a number of fixes on some of the built-in schemas for the Parser utility.

Specifically, the queryStringParameters, multiValueQueryStringParameters, and body fields in the APIGatewayProxyEventSchema have been converted to .nullable() to account for them being set to null in some types of requests.

Likewise, the etag field in the S3EventNotificationEventBridgeDetailSchema has been made .optional() since it's not included when an object being deleted on S3 sends a notification via Amazon EventBridge.

Finally, the principalOrgId and cognitoIdentity fields in the APIGatewayProxyEventV2Schema have been converted to .nullish().

We want to thank everyone who has taken the time to test the first beta for the Parser utility and especially those who have also reported issues they might have encountered. Thank you for making Powertools for AWS Lambda better for everyone!

Tracer

In March 2024, AWS announced that AWS SDK for JavaScript v2 will reach end-of-support in September 8, 2025. In response to this announcement, and to align with the warnings already being emitted by the AWS SDK, with this release we are marking the captureAWS and captureAWSClient methods as deprecated.

This announcement does not impact the methods and you are free to continue using them. The deprecation tag serves only as a gentle nudge to consider a migration to the newer AWS SDK for JavaScript v3 which can be instrumented via the captureAWSv3Client.

The two methods we are marking as deprecated today will be removed in the next major release, which as of today has no planned date.

Acknowledgements

Congratulations to @​blytheaw for getting their first PR merged 🎉 and thanks also to @​arnabrahman for another successful contribution 🙏!

Workshop

For those of you wanting to get a deeper introduction to Powertools for AWS Lambda, you can now try our official self-paced workshop titled “Accelerate your serverless journey with Powertools for AWS Lambda”.

Miscellaneous

We are happy to also share that we have restarted working on the RFC process for the upcoming Event Handler utility. Last week we have published a first decision log on our direction in terms of routing implementation where we have decided to move forward with a new implementation rather than taking a 3rd party library as dependency. The next step will be to finalize the main RFC for how the API and Developer Experience (DX) for the utility will look like.

In parallel, we have started refreshing the API docs for the utilities starting with the Commons utility, which is mainly used internally by other utilities. The goal for this workstream is to standardize the docstrings and contextual documentation so that you can have more details on what different public APIs do.

Changes

... (truncated)

Changelog

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

2.1.1 (2024-05-14)

Bug Fixes

Commits

[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=@aws-lambda-powertools/parameters&package-manager=npm_and_yarn&previous-version=2.1.0&new-version=2.1.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) ---
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 ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Signed-off-by: dependabot[bot] Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> --- package-lock.json | 16 ++++++++-------- packages/statusLambda/package.json | 2 +- 2 files changed, 9 insertions(+), 9 deletions(-) diff --git a/package-lock.json b/package-lock.json index 7f266105..b327aa98 100644 --- a/package-lock.json +++ b/package-lock.json @@ -56,9 +56,9 @@ } }, "node_modules/@aws-lambda-powertools/commons": { - "version": "2.1.0", - "resolved": "https://registry.npmjs.org/@aws-lambda-powertools/commons/-/commons-2.1.0.tgz", - "integrity": "sha512-pFIlGa2IreeQ8elvuWlqxp6q/R4Zx7EqzCAlj0yXg12XpQprF4BhuE3NpeF09MA/QkyCot5Hxu3kG95E35XETA==" + "version": "2.1.1", + "resolved": "https://registry.npmjs.org/@aws-lambda-powertools/commons/-/commons-2.1.1.tgz", + "integrity": "sha512-QlvZLVJM4yXlO6mpYlYwWGaLCZTJg8WfsIH8/eT061n4BdBljW/VHMj59sHp/IljQn8HE/VdHKYHqM6vPJjYJw==" }, "node_modules/@aws-lambda-powertools/logger": { "version": "2.1.0", @@ -78,11 +78,11 @@ } }, "node_modules/@aws-lambda-powertools/parameters": { - "version": "2.1.0", - "resolved": "https://registry.npmjs.org/@aws-lambda-powertools/parameters/-/parameters-2.1.0.tgz", - "integrity": "sha512-waUA3nfWgRUTuL5YKiN4gRFohn+RogA6akatChQaqLXAaOBrHKiX8UXERqYBk8F5IacV5XLQpDw2vjWqF6fE4g==", + "version": "2.1.1", + "resolved": "https://registry.npmjs.org/@aws-lambda-powertools/parameters/-/parameters-2.1.1.tgz", + "integrity": "sha512-FfmdE0anTY0ZkWPmyYt6hm7/Gf5TrTxAXlEQ/+HB+8XJTBZrpwIoegVbvuEDIgWyU+DlviwD/qpl/JS47VTnEw==", "dependencies": { - "@aws-lambda-powertools/commons": "^2.1.0" + "@aws-lambda-powertools/commons": "^2.1.1" }, "peerDependencies": { "@aws-sdk/client-appconfigdata": ">=3.x", @@ -6853,7 +6853,7 @@ "dependencies": { "@aws-lambda-powertools/commons": "^2.0.4", "@aws-lambda-powertools/logger": "^2.1.0", - "@aws-lambda-powertools/parameters": "^2.1.0", + "@aws-lambda-powertools/parameters": "^2.1.1", "@middy/core": "^5.3.4", "@middy/input-output-logger": "^5.3.4", "@nhs/fhir-middy-error-handler": "^2.0.6", diff --git a/packages/statusLambda/package.json b/packages/statusLambda/package.json index 8145bd2b..d33fd7b9 100644 --- a/packages/statusLambda/package.json +++ b/packages/statusLambda/package.json @@ -15,7 +15,7 @@ "dependencies": { "@aws-lambda-powertools/commons": "^2.0.4", "@aws-lambda-powertools/logger": "^2.1.0", - "@aws-lambda-powertools/parameters": "^2.1.0", + "@aws-lambda-powertools/parameters": "^2.1.1", "@middy/core": "^5.3.4", "@middy/input-output-logger": "^5.3.4", "@nhs/fhir-middy-error-handler": "^2.0.6",