Skip to content

Commit 49d40b3

Browse files
fix(lambda): bump the aws-powertools group in /lambdas with 4 updates (#4425)
Bumps the aws-powertools group in /lambdas with 4 updates: [@aws-lambda-powertools/parameters](https://github.com/aws-powertools/powertools-lambda-typescript), [@aws-lambda-powertools/logger](https://github.com/aws-powertools/powertools-lambda-typescript), [@aws-lambda-powertools/metrics](https://github.com/aws-powertools/powertools-lambda-typescript) and [@aws-lambda-powertools/tracer](https://github.com/aws-powertools/powertools-lambda-typescript). Updates `@aws-lambda-powertools/parameters` from 2.13.1 to 2.14.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/aws-powertools/powertools-lambda-typescript/releases"><code>@​aws-lambda-powertools/parameters</code>'s releases</a>.</em></p> <blockquote> <h2>v2.14.0</h2> <h2>Summary</h2> <p>In this release we fixed a bug in Logger that allowed customer keys to replace service keys in logs and potentially leading to data loss. We also improved the Parser experience by adding a new schema for AWS Transfer Family and updated how we parse S3 Notification events delivered via SQS.</p> <p>Finally, we also started publishing public SSM Parameters to easily look up Lambda layer ARNs 🔥</p> <p>⭐️ Thanks to <a href="https://github.com/VatsalGoel3"><code>@​VatsalGoel3</code></a> and <a href="https://github.com/cyrildewit"><code>@​cyrildewit</code></a> for their contributions to this release!</p> <h3>Working with S3 events delivered via SQS</h3> <blockquote> <p><a href="https://docs.powertools.aws.dev/lambda/typescript/latest/utilities/parser/#built-in-schemas">Docs</a></p> </blockquote> <p>When sending S3 Notification events to SQS, the events are JSON-serialized and delivered as strings in the SQS message body. We have updated the <code>S3SqsEventNotificationSchema</code> built-in schema to correctly transform the message body into an object during event parsing, fixing this bug in the original implementation.</p> <p><img src="https://github.com/user-attachments/assets/f4cdf0b1-1ae2-42e4-8954-48b4d2aa3876" alt="carbon-3" /></p> <h3>New AWS Transfer Family schema</h3> <blockquote> <p><a href="https://docs.powertools.aws.dev/lambda/typescript/latest/utilities/parser/#built-in-schemas">Docs</a></p> </blockquote> <p>You can now work with AWS Transfer Family events using the new <code>TransferFamilySchema</code> built-in schema. This is useful when building Lambda functions that act as custom authorizers for AWS Transfer Family.</p> <p><img src="https://github.com/user-attachments/assets/00b918ad-b4c6-4a50-9846-b13972e3835e" alt="carbon-4" /></p> <h3>Prevent overwriting Logger standard keys</h3> <blockquote> <p><a href="https://docs.powertools.aws.dev/lambda/typescript/latest/core/logger/#standard-structured-keys">Docs</a></p> </blockquote> <p>Before this release, customers could overwrite the standard Logger keys such as level, message, service or even <code>timestamp</code> with their own value. In most cases this was unintentional and there was no warning, so customers could not find their expected logs and would not notice this issue. Now, the standard log keys are considered as reserved and any attempt to overwrite them will log a warning.</p> <p><img src="https://github.com/user-attachments/assets/11e0c994-91c4-48ca-8d89-6d46a8064b16" alt="carbon-5" /></p> <h3>Lambda layer SSM Parameter lookup</h3> <blockquote> <p><a href="https://docs.powertools.aws.dev/lambda/typescript/latest/#lambda-layer_1">Docs</a></p> </blockquote> <p>You can now use our public SSM Parameters to easily look up the ARNs for our Powertools for AWS Lambda layers. For example, you can use the <code>/aws/service/powertools/typescript/generic/all/latest</code> to fetch the ARN of the current latest layer or <code>/aws/service/powertools/beta/typescript/generic/all/&lt;semantic-version&gt;</code> to get the one for a specific version published on npmjs.com.</p> <p>This makes it easy to attach the layer to your functions without having to look at the documentation. You can fetch the ARN using the AWS CLI:</p> <pre lang="sh"><code>aws ssm get-parameter --name=/aws/service/powertools/typescript/generic/all/latest </code></pre> <p>Or perform the lookup directly in your IaC template, below is an example of how to use it with AWS CDK but you can do the same with AWS SAM, Terraform, and plain CloudFormation templates among others:</p> <pre lang="ts"><code>const powertoolsLayerArn = StringParameter.fromStringParameterAttributes(self, 'PTLayerArn', { parameterName: '/aws/service/powertools/typescript/generic/all/latest' &lt;/tr&gt;&lt;/table&gt; </code></pre> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/aws-powertools/powertools-lambda-typescript/blob/main/CHANGELOG.md"><code>@​aws-lambda-powertools/parameters</code>'s changelog</a>.</em></p> <blockquote> <h1><a href="https://github.com/aws-powertools/powertools-lambda-typescript/compare/v2.13.1...v2.14.0">2.14.0</a> (2025-02-10)</h1> <h3>Bug Fixes</h3> <ul> <li><strong>logger:</strong> prevent overwriting standard keys (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3553">#3553</a>) (<a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/f0bdf3cdb1fe25ff7baea352215f41501ca6c5c2">f0bdf3c</a>)</li> <li><strong>parser:</strong> parse sqs record body field as JSON and S3Schema in S3SqsEventNoificationRecordSchema (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3529">#3529</a>) (<a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/bcd4b9f7864543b25c57143c2903ed68c16d3987">bcd4b9f</a>)</li> </ul> <h3>Features</h3> <ul> <li><strong>ci:</strong> Add advanced automation (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3438">#3438</a>) (<a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/4e9ff0717223f8305eda684608ce1435489b9749">4e9ff07</a>)</li> <li><strong>parser:</strong> add TransferFamilySchema for AWS Transfer Family events (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3575">#3575</a>) (<a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/2c27c5e717ff6a8f9b54148dbde3ab7dc83b5baf">2c27c5e</a>)</li> <li><strong>parser:</strong> simplify <code>ParseResult</code> and <code>parse</code> inference (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3568">#3568</a>) (<a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/95762ade4b51fc40860302dd77a97819dac44a98">95762ad</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/a40b326b6d7562a7607606d18f92b69b5790a136"><code>a40b326</code></a> chore(ci): bump version to 2.14.0 (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3582">#3582</a>)</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/9060e54039e4f7ed5233567d10f07d4691621150"><code>9060e54</code></a> chore(deps-dev): bump typedoc from 0.27.6 to 0.27.7 in the typescript group a...</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/3e1aaa8eac58c305b651f4dfc6b795f3ba1d59a5"><code>3e1aaa8</code></a> chore(deps): bump the aws-sdk-v3 group across 1 directory with 9 updates (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3579">#3579</a>)</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/a59b0970ac4acced3c2e3058e5bafdf99bc4d2c3"><code>a59b097</code></a> chore(ci): remove pinned actions &amp; pkg versions (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3576">#3576</a>)</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/a5708be88044da4598121c810481c9b2ba4f1dc6"><code>a5708be</code></a> chore(deps): bump esbuild from 0.24.2 to 0.25.0 (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3581">#3581</a>)</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/a5cc74f10d4bb4da01119c40e84e92069f7f295b"><code>a5cc74f</code></a> docs: add SSM examples to docs (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3577">#3577</a>)</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/2c27c5e717ff6a8f9b54148dbde3ab7dc83b5baf"><code>2c27c5e</code></a> feat(parser): add TransferFamilySchema for AWS Transfer Family events (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3575">#3575</a>)</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/66364b5f9c74df7eefc695aab788c1f4008e7250"><code>66364b5</code></a> chore(deps): bump squidfunk/mkdocs-material from <code>7e841df</code> to <code>c62453b</code> in /d...</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/8df04303252b7c4a23f29b54eb7af60bfbd27b39"><code>8df0430</code></a> chore(deps): bump the aws-cdk group across 1 directory with 2 updates (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3569">#3569</a>)</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/3ae87c3cbb317443eb5726f56009ccc90f8df9ff"><code>3ae87c3</code></a> chore(deps): bump the aws-sdk-v3 group across 1 directory with 9 updates (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3570">#3570</a>)</li> <li>Additional commits viewable in <a href="https://github.com/aws-powertools/powertools-lambda-typescript/compare/v2.13.1...v2.14.0">compare view</a></li> </ul> </details> <br /> Updates `@aws-lambda-powertools/logger` from 2.13.1 to 2.14.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/aws-powertools/powertools-lambda-typescript/releases"><code>@​aws-lambda-powertools/logger</code>'s releases</a>.</em></p> <blockquote> <h2>v2.14.0</h2> <h2>Summary</h2> <p>In this release we fixed a bug in Logger that allowed customer keys to replace service keys in logs and potentially leading to data loss. We also improved the Parser experience by adding a new schema for AWS Transfer Family and updated how we parse S3 Notification events delivered via SQS.</p> <p>Finally, we also started publishing public SSM Parameters to easily look up Lambda layer ARNs 🔥</p> <p>⭐️ Thanks to <a href="https://github.com/VatsalGoel3"><code>@​VatsalGoel3</code></a> and <a href="https://github.com/cyrildewit"><code>@​cyrildewit</code></a> for their contributions to this release!</p> <h3>Working with S3 events delivered via SQS</h3> <blockquote> <p><a href="https://docs.powertools.aws.dev/lambda/typescript/latest/utilities/parser/#built-in-schemas">Docs</a></p> </blockquote> <p>When sending S3 Notification events to SQS, the events are JSON-serialized and delivered as strings in the SQS message body. We have updated the <code>S3SqsEventNotificationSchema</code> built-in schema to correctly transform the message body into an object during event parsing, fixing this bug in the original implementation.</p> <p><img src="https://github.com/user-attachments/assets/f4cdf0b1-1ae2-42e4-8954-48b4d2aa3876" alt="carbon-3" /></p> <h3>New AWS Transfer Family schema</h3> <blockquote> <p><a href="https://docs.powertools.aws.dev/lambda/typescript/latest/utilities/parser/#built-in-schemas">Docs</a></p> </blockquote> <p>You can now work with AWS Transfer Family events using the new <code>TransferFamilySchema</code> built-in schema. This is useful when building Lambda functions that act as custom authorizers for AWS Transfer Family.</p> <p><img src="https://github.com/user-attachments/assets/00b918ad-b4c6-4a50-9846-b13972e3835e" alt="carbon-4" /></p> <h3>Prevent overwriting Logger standard keys</h3> <blockquote> <p><a href="https://docs.powertools.aws.dev/lambda/typescript/latest/core/logger/#standard-structured-keys">Docs</a></p> </blockquote> <p>Before this release, customers could overwrite the standard Logger keys such as level, message, service or even <code>timestamp</code> with their own value. In most cases this was unintentional and there was no warning, so customers could not find their expected logs and would not notice this issue. Now, the standard log keys are considered as reserved and any attempt to overwrite them will log a warning.</p> <p><img src="https://github.com/user-attachments/assets/11e0c994-91c4-48ca-8d89-6d46a8064b16" alt="carbon-5" /></p> <h3>Lambda layer SSM Parameter lookup</h3> <blockquote> <p><a href="https://docs.powertools.aws.dev/lambda/typescript/latest/#lambda-layer_1">Docs</a></p> </blockquote> <p>You can now use our public SSM Parameters to easily look up the ARNs for our Powertools for AWS Lambda layers. For example, you can use the <code>/aws/service/powertools/typescript/generic/all/latest</code> to fetch the ARN of the current latest layer or <code>/aws/service/powertools/beta/typescript/generic/all/&lt;semantic-version&gt;</code> to get the one for a specific version published on npmjs.com.</p> <p>This makes it easy to attach the layer to your functions without having to look at the documentation. You can fetch the ARN using the AWS CLI:</p> <pre lang="sh"><code>aws ssm get-parameter --name=/aws/service/powertools/typescript/generic/all/latest </code></pre> <p>Or perform the lookup directly in your IaC template, below is an example of how to use it with AWS CDK but you can do the same with AWS SAM, Terraform, and plain CloudFormation templates among others:</p> <pre lang="ts"><code>const powertoolsLayerArn = StringParameter.fromStringParameterAttributes(self, 'PTLayerArn', { parameterName: '/aws/service/powertools/typescript/generic/all/latest' &lt;/tr&gt;&lt;/table&gt; </code></pre> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/aws-powertools/powertools-lambda-typescript/blob/main/CHANGELOG.md"><code>@​aws-lambda-powertools/logger</code>'s changelog</a>.</em></p> <blockquote> <h1><a href="https://github.com/aws-powertools/powertools-lambda-typescript/compare/v2.13.1...v2.14.0">2.14.0</a> (2025-02-10)</h1> <h3>Bug Fixes</h3> <ul> <li><strong>logger:</strong> prevent overwriting standard keys (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3553">#3553</a>) (<a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/f0bdf3cdb1fe25ff7baea352215f41501ca6c5c2">f0bdf3c</a>)</li> <li><strong>parser:</strong> parse sqs record body field as JSON and S3Schema in S3SqsEventNoificationRecordSchema (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3529">#3529</a>) (<a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/bcd4b9f7864543b25c57143c2903ed68c16d3987">bcd4b9f</a>)</li> </ul> <h3>Features</h3> <ul> <li><strong>ci:</strong> Add advanced automation (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3438">#3438</a>) (<a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/4e9ff0717223f8305eda684608ce1435489b9749">4e9ff07</a>)</li> <li><strong>parser:</strong> add TransferFamilySchema for AWS Transfer Family events (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3575">#3575</a>) (<a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/2c27c5e717ff6a8f9b54148dbde3ab7dc83b5baf">2c27c5e</a>)</li> <li><strong>parser:</strong> simplify <code>ParseResult</code> and <code>parse</code> inference (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3568">#3568</a>) (<a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/95762ade4b51fc40860302dd77a97819dac44a98">95762ad</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/a40b326b6d7562a7607606d18f92b69b5790a136"><code>a40b326</code></a> chore(ci): bump version to 2.14.0 (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3582">#3582</a>)</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/9060e54039e4f7ed5233567d10f07d4691621150"><code>9060e54</code></a> chore(deps-dev): bump typedoc from 0.27.6 to 0.27.7 in the typescript group a...</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/3e1aaa8eac58c305b651f4dfc6b795f3ba1d59a5"><code>3e1aaa8</code></a> chore(deps): bump the aws-sdk-v3 group across 1 directory with 9 updates (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3579">#3579</a>)</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/a59b0970ac4acced3c2e3058e5bafdf99bc4d2c3"><code>a59b097</code></a> chore(ci): remove pinned actions &amp; pkg versions (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3576">#3576</a>)</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/a5708be88044da4598121c810481c9b2ba4f1dc6"><code>a5708be</code></a> chore(deps): bump esbuild from 0.24.2 to 0.25.0 (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3581">#3581</a>)</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/a5cc74f10d4bb4da01119c40e84e92069f7f295b"><code>a5cc74f</code></a> docs: add SSM examples to docs (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3577">#3577</a>)</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/2c27c5e717ff6a8f9b54148dbde3ab7dc83b5baf"><code>2c27c5e</code></a> feat(parser): add TransferFamilySchema for AWS Transfer Family events (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3575">#3575</a>)</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/66364b5f9c74df7eefc695aab788c1f4008e7250"><code>66364b5</code></a> chore(deps): bump squidfunk/mkdocs-material from <code>7e841df</code> to <code>c62453b</code> in /d...</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/8df04303252b7c4a23f29b54eb7af60bfbd27b39"><code>8df0430</code></a> chore(deps): bump the aws-cdk group across 1 directory with 2 updates (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3569">#3569</a>)</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/3ae87c3cbb317443eb5726f56009ccc90f8df9ff"><code>3ae87c3</code></a> chore(deps): bump the aws-sdk-v3 group across 1 directory with 9 updates (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3570">#3570</a>)</li> <li>Additional commits viewable in <a href="https://github.com/aws-powertools/powertools-lambda-typescript/compare/v2.13.1...v2.14.0">compare view</a></li> </ul> </details> <br /> Updates `@aws-lambda-powertools/metrics` from 2.13.1 to 2.14.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/aws-powertools/powertools-lambda-typescript/releases"><code>@​aws-lambda-powertools/metrics</code>'s releases</a>.</em></p> <blockquote> <h2>v2.14.0</h2> <h2>Summary</h2> <p>In this release we fixed a bug in Logger that allowed customer keys to replace service keys in logs and potentially leading to data loss. We also improved the Parser experience by adding a new schema for AWS Transfer Family and updated how we parse S3 Notification events delivered via SQS.</p> <p>Finally, we also started publishing public SSM Parameters to easily look up Lambda layer ARNs 🔥</p> <p>⭐️ Thanks to <a href="https://github.com/VatsalGoel3"><code>@​VatsalGoel3</code></a> and <a href="https://github.com/cyrildewit"><code>@​cyrildewit</code></a> for their contributions to this release!</p> <h3>Working with S3 events delivered via SQS</h3> <blockquote> <p><a href="https://docs.powertools.aws.dev/lambda/typescript/latest/utilities/parser/#built-in-schemas">Docs</a></p> </blockquote> <p>When sending S3 Notification events to SQS, the events are JSON-serialized and delivered as strings in the SQS message body. We have updated the <code>S3SqsEventNotificationSchema</code> built-in schema to correctly transform the message body into an object during event parsing, fixing this bug in the original implementation.</p> <p><img src="https://github.com/user-attachments/assets/f4cdf0b1-1ae2-42e4-8954-48b4d2aa3876" alt="carbon-3" /></p> <h3>New AWS Transfer Family schema</h3> <blockquote> <p><a href="https://docs.powertools.aws.dev/lambda/typescript/latest/utilities/parser/#built-in-schemas">Docs</a></p> </blockquote> <p>You can now work with AWS Transfer Family events using the new <code>TransferFamilySchema</code> built-in schema. This is useful when building Lambda functions that act as custom authorizers for AWS Transfer Family.</p> <p><img src="https://github.com/user-attachments/assets/00b918ad-b4c6-4a50-9846-b13972e3835e" alt="carbon-4" /></p> <h3>Prevent overwriting Logger standard keys</h3> <blockquote> <p><a href="https://docs.powertools.aws.dev/lambda/typescript/latest/core/logger/#standard-structured-keys">Docs</a></p> </blockquote> <p>Before this release, customers could overwrite the standard Logger keys such as level, message, service or even <code>timestamp</code> with their own value. In most cases this was unintentional and there was no warning, so customers could not find their expected logs and would not notice this issue. Now, the standard log keys are considered as reserved and any attempt to overwrite them will log a warning.</p> <p><img src="https://github.com/user-attachments/assets/11e0c994-91c4-48ca-8d89-6d46a8064b16" alt="carbon-5" /></p> <h3>Lambda layer SSM Parameter lookup</h3> <blockquote> <p><a href="https://docs.powertools.aws.dev/lambda/typescript/latest/#lambda-layer_1">Docs</a></p> </blockquote> <p>You can now use our public SSM Parameters to easily look up the ARNs for our Powertools for AWS Lambda layers. For example, you can use the <code>/aws/service/powertools/typescript/generic/all/latest</code> to fetch the ARN of the current latest layer or <code>/aws/service/powertools/beta/typescript/generic/all/&lt;semantic-version&gt;</code> to get the one for a specific version published on npmjs.com.</p> <p>This makes it easy to attach the layer to your functions without having to look at the documentation. You can fetch the ARN using the AWS CLI:</p> <pre lang="sh"><code>aws ssm get-parameter --name=/aws/service/powertools/typescript/generic/all/latest </code></pre> <p>Or perform the lookup directly in your IaC template, below is an example of how to use it with AWS CDK but you can do the same with AWS SAM, Terraform, and plain CloudFormation templates among others:</p> <pre lang="ts"><code>const powertoolsLayerArn = StringParameter.fromStringParameterAttributes(self, 'PTLayerArn', { parameterName: '/aws/service/powertools/typescript/generic/all/latest' &lt;/tr&gt;&lt;/table&gt; </code></pre> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/aws-powertools/powertools-lambda-typescript/blob/main/CHANGELOG.md"><code>@​aws-lambda-powertools/metrics</code>'s changelog</a>.</em></p> <blockquote> <h1><a href="https://github.com/aws-powertools/powertools-lambda-typescript/compare/v2.13.1...v2.14.0">2.14.0</a> (2025-02-10)</h1> <h3>Bug Fixes</h3> <ul> <li><strong>logger:</strong> prevent overwriting standard keys (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3553">#3553</a>) (<a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/f0bdf3cdb1fe25ff7baea352215f41501ca6c5c2">f0bdf3c</a>)</li> <li><strong>parser:</strong> parse sqs record body field as JSON and S3Schema in S3SqsEventNoificationRecordSchema (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3529">#3529</a>) (<a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/bcd4b9f7864543b25c57143c2903ed68c16d3987">bcd4b9f</a>)</li> </ul> <h3>Features</h3> <ul> <li><strong>ci:</strong> Add advanced automation (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3438">#3438</a>) (<a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/4e9ff0717223f8305eda684608ce1435489b9749">4e9ff07</a>)</li> <li><strong>parser:</strong> add TransferFamilySchema for AWS Transfer Family events (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3575">#3575</a>) (<a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/2c27c5e717ff6a8f9b54148dbde3ab7dc83b5baf">2c27c5e</a>)</li> <li><strong>parser:</strong> simplify <code>ParseResult</code> and <code>parse</code> inference (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3568">#3568</a>) (<a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/95762ade4b51fc40860302dd77a97819dac44a98">95762ad</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/a40b326b6d7562a7607606d18f92b69b5790a136"><code>a40b326</code></a> chore(ci): bump version to 2.14.0 (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3582">#3582</a>)</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/9060e54039e4f7ed5233567d10f07d4691621150"><code>9060e54</code></a> chore(deps-dev): bump typedoc from 0.27.6 to 0.27.7 in the typescript group a...</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/3e1aaa8eac58c305b651f4dfc6b795f3ba1d59a5"><code>3e1aaa8</code></a> chore(deps): bump the aws-sdk-v3 group across 1 directory with 9 updates (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3579">#3579</a>)</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/a59b0970ac4acced3c2e3058e5bafdf99bc4d2c3"><code>a59b097</code></a> chore(ci): remove pinned actions &amp; pkg versions (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3576">#3576</a>)</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/a5708be88044da4598121c810481c9b2ba4f1dc6"><code>a5708be</code></a> chore(deps): bump esbuild from 0.24.2 to 0.25.0 (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3581">#3581</a>)</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/a5cc74f10d4bb4da01119c40e84e92069f7f295b"><code>a5cc74f</code></a> docs: add SSM examples to docs (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3577">#3577</a>)</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/2c27c5e717ff6a8f9b54148dbde3ab7dc83b5baf"><code>2c27c5e</code></a> feat(parser): add TransferFamilySchema for AWS Transfer Family events (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3575">#3575</a>)</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/66364b5f9c74df7eefc695aab788c1f4008e7250"><code>66364b5</code></a> chore(deps): bump squidfunk/mkdocs-material from <code>7e841df</code> to <code>c62453b</code> in /d...</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/8df04303252b7c4a23f29b54eb7af60bfbd27b39"><code>8df0430</code></a> chore(deps): bump the aws-cdk group across 1 directory with 2 updates (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3569">#3569</a>)</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/3ae87c3cbb317443eb5726f56009ccc90f8df9ff"><code>3ae87c3</code></a> chore(deps): bump the aws-sdk-v3 group across 1 directory with 9 updates (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3570">#3570</a>)</li> <li>Additional commits viewable in <a href="https://github.com/aws-powertools/powertools-lambda-typescript/compare/v2.13.1...v2.14.0">compare view</a></li> </ul> </details> <br /> Updates `@aws-lambda-powertools/tracer` from 2.13.1 to 2.14.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/aws-powertools/powertools-lambda-typescript/releases"><code>@​aws-lambda-powertools/tracer</code>'s releases</a>.</em></p> <blockquote> <h2>v2.14.0</h2> <h2>Summary</h2> <p>In this release we fixed a bug in Logger that allowed customer keys to replace service keys in logs and potentially leading to data loss. We also improved the Parser experience by adding a new schema for AWS Transfer Family and updated how we parse S3 Notification events delivered via SQS.</p> <p>Finally, we also started publishing public SSM Parameters to easily look up Lambda layer ARNs 🔥</p> <p>⭐️ Thanks to <a href="https://github.com/VatsalGoel3"><code>@​VatsalGoel3</code></a> and <a href="https://github.com/cyrildewit"><code>@​cyrildewit</code></a> for their contributions to this release!</p> <h3>Working with S3 events delivered via SQS</h3> <blockquote> <p><a href="https://docs.powertools.aws.dev/lambda/typescript/latest/utilities/parser/#built-in-schemas">Docs</a></p> </blockquote> <p>When sending S3 Notification events to SQS, the events are JSON-serialized and delivered as strings in the SQS message body. We have updated the <code>S3SqsEventNotificationSchema</code> built-in schema to correctly transform the message body into an object during event parsing, fixing this bug in the original implementation.</p> <p><img src="https://github.com/user-attachments/assets/f4cdf0b1-1ae2-42e4-8954-48b4d2aa3876" alt="carbon-3" /></p> <h3>New AWS Transfer Family schema</h3> <blockquote> <p><a href="https://docs.powertools.aws.dev/lambda/typescript/latest/utilities/parser/#built-in-schemas">Docs</a></p> </blockquote> <p>You can now work with AWS Transfer Family events using the new <code>TransferFamilySchema</code> built-in schema. This is useful when building Lambda functions that act as custom authorizers for AWS Transfer Family.</p> <p><img src="https://github.com/user-attachments/assets/00b918ad-b4c6-4a50-9846-b13972e3835e" alt="carbon-4" /></p> <h3>Prevent overwriting Logger standard keys</h3> <blockquote> <p><a href="https://docs.powertools.aws.dev/lambda/typescript/latest/core/logger/#standard-structured-keys">Docs</a></p> </blockquote> <p>Before this release, customers could overwrite the standard Logger keys such as level, message, service or even <code>timestamp</code> with their own value. In most cases this was unintentional and there was no warning, so customers could not find their expected logs and would not notice this issue. Now, the standard log keys are considered as reserved and any attempt to overwrite them will log a warning.</p> <p><img src="https://github.com/user-attachments/assets/11e0c994-91c4-48ca-8d89-6d46a8064b16" alt="carbon-5" /></p> <h3>Lambda layer SSM Parameter lookup</h3> <blockquote> <p><a href="https://docs.powertools.aws.dev/lambda/typescript/latest/#lambda-layer_1">Docs</a></p> </blockquote> <p>You can now use our public SSM Parameters to easily look up the ARNs for our Powertools for AWS Lambda layers. For example, you can use the <code>/aws/service/powertools/typescript/generic/all/latest</code> to fetch the ARN of the current latest layer or <code>/aws/service/powertools/beta/typescript/generic/all/&lt;semantic-version&gt;</code> to get the one for a specific version published on npmjs.com.</p> <p>This makes it easy to attach the layer to your functions without having to look at the documentation. You can fetch the ARN using the AWS CLI:</p> <pre lang="sh"><code>aws ssm get-parameter --name=/aws/service/powertools/typescript/generic/all/latest </code></pre> <p>Or perform the lookup directly in your IaC template, below is an example of how to use it with AWS CDK but you can do the same with AWS SAM, Terraform, and plain CloudFormation templates among others:</p> <pre lang="ts"><code>const powertoolsLayerArn = StringParameter.fromStringParameterAttributes(self, 'PTLayerArn', { parameterName: '/aws/service/powertools/typescript/generic/all/latest' &lt;/tr&gt;&lt;/table&gt; </code></pre> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/aws-powertools/powertools-lambda-typescript/blob/main/CHANGELOG.md"><code>@​aws-lambda-powertools/tracer</code>'s changelog</a>.</em></p> <blockquote> <h1><a href="https://github.com/aws-powertools/powertools-lambda-typescript/compare/v2.13.1...v2.14.0">2.14.0</a> (2025-02-10)</h1> <h3>Bug Fixes</h3> <ul> <li><strong>logger:</strong> prevent overwriting standard keys (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3553">#3553</a>) (<a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/f0bdf3cdb1fe25ff7baea352215f41501ca6c5c2">f0bdf3c</a>)</li> <li><strong>parser:</strong> parse sqs record body field as JSON and S3Schema in S3SqsEventNoificationRecordSchema (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3529">#3529</a>) (<a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/bcd4b9f7864543b25c57143c2903ed68c16d3987">bcd4b9f</a>)</li> </ul> <h3>Features</h3> <ul> <li><strong>ci:</strong> Add advanced automation (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3438">#3438</a>) (<a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/4e9ff0717223f8305eda684608ce1435489b9749">4e9ff07</a>)</li> <li><strong>parser:</strong> add TransferFamilySchema for AWS Transfer Family events (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3575">#3575</a>) (<a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/2c27c5e717ff6a8f9b54148dbde3ab7dc83b5baf">2c27c5e</a>)</li> <li><strong>parser:</strong> simplify <code>ParseResult</code> and <code>parse</code> inference (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3568">#3568</a>) (<a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/95762ade4b51fc40860302dd77a97819dac44a98">95762ad</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/a40b326b6d7562a7607606d18f92b69b5790a136"><code>a40b326</code></a> chore(ci): bump version to 2.14.0 (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3582">#3582</a>)</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/9060e54039e4f7ed5233567d10f07d4691621150"><code>9060e54</code></a> chore(deps-dev): bump typedoc from 0.27.6 to 0.27.7 in the typescript group a...</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/3e1aaa8eac58c305b651f4dfc6b795f3ba1d59a5"><code>3e1aaa8</code></a> chore(deps): bump the aws-sdk-v3 group across 1 directory with 9 updates (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3579">#3579</a>)</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/a59b0970ac4acced3c2e3058e5bafdf99bc4d2c3"><code>a59b097</code></a> chore(ci): remove pinned actions &amp; pkg versions (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3576">#3576</a>)</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/a5708be88044da4598121c810481c9b2ba4f1dc6"><code>a5708be</code></a> chore(deps): bump esbuild from 0.24.2 to 0.25.0 (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3581">#3581</a>)</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/a5cc74f10d4bb4da01119c40e84e92069f7f295b"><code>a5cc74f</code></a> docs: add SSM examples to docs (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3577">#3577</a>)</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/2c27c5e717ff6a8f9b54148dbde3ab7dc83b5baf"><code>2c27c5e</code></a> feat(parser): add TransferFamilySchema for AWS Transfer Family events (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3575">#3575</a>)</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/66364b5f9c74df7eefc695aab788c1f4008e7250"><code>66364b5</code></a> chore(deps): bump squidfunk/mkdocs-material from <code>7e841df</code> to <code>c62453b</code> in /d...</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/8df04303252b7c4a23f29b54eb7af60bfbd27b39"><code>8df0430</code></a> chore(deps): bump the aws-cdk group across 1 directory with 2 updates (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3569">#3569</a>)</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/3ae87c3cbb317443eb5726f56009ccc90f8df9ff"><code>3ae87c3</code></a> chore(deps): bump the aws-sdk-v3 group across 1 directory with 9 updates (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/3570">#3570</a>)</li> <li>Additional commits viewable in <a href="https://github.com/aws-powertools/powertools-lambda-typescript/compare/v2.13.1...v2.14.0">compare view</a></li> </ul> </details> <br /> 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) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 </details> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
1 parent 945bff1 commit 49d40b3

File tree

3 files changed

+37
-37
lines changed

3 files changed

+37
-37
lines changed

lambdas/functions/control-plane/package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@
4040
"dependencies": {
4141
"@aws-github-runner/aws-powertools-util": "*",
4242
"@aws-github-runner/aws-ssm-util": "*",
43-
"@aws-lambda-powertools/parameters": "^2.13.1",
43+
"@aws-lambda-powertools/parameters": "^2.14.0",
4444
"@aws-sdk/client-ec2": "^3.749.0",
4545
"@aws-sdk/client-sqs": "^3.749.0",
4646
"@aws-sdk/types": "^3.734.0",

lambdas/libs/aws-powertools-util/package.json

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -34,9 +34,9 @@
3434
"typescript": "^5.7.3"
3535
},
3636
"dependencies": {
37-
"@aws-lambda-powertools/logger": "^2.13.1",
38-
"@aws-lambda-powertools/metrics": "^2.13.1",
39-
"@aws-lambda-powertools/tracer": "^2.13.1",
37+
"@aws-lambda-powertools/logger": "^2.14.0",
38+
"@aws-lambda-powertools/metrics": "^2.14.0",
39+
"@aws-lambda-powertools/tracer": "^2.14.0",
4040
"aws-lambda": "^1.0.7"
4141
},
4242
"nx": {

lambdas/yarn.lock

Lines changed: 33 additions & 33 deletions
Original file line numberDiff line numberDiff line change
@@ -134,9 +134,9 @@ __metadata:
134134
version: 0.0.0-use.local
135135
resolution: "@aws-github-runner/aws-powertools-util@workspace:libs/aws-powertools-util"
136136
dependencies:
137-
"@aws-lambda-powertools/logger": "npm:^2.13.1"
138-
"@aws-lambda-powertools/metrics": "npm:^2.13.1"
139-
"@aws-lambda-powertools/tracer": "npm:^2.13.1"
137+
"@aws-lambda-powertools/logger": "npm:^2.14.0"
138+
"@aws-lambda-powertools/metrics": "npm:^2.14.0"
139+
"@aws-lambda-powertools/tracer": "npm:^2.14.0"
140140
"@trivago/prettier-plugin-sort-imports": "npm:^5.2.2"
141141
"@types/aws-lambda": "npm:^8.10.146"
142142
"@types/jest": "npm:^29.5.14"
@@ -193,7 +193,7 @@ __metadata:
193193
dependencies:
194194
"@aws-github-runner/aws-powertools-util": "npm:*"
195195
"@aws-github-runner/aws-ssm-util": "npm:*"
196-
"@aws-lambda-powertools/parameters": "npm:^2.13.1"
196+
"@aws-lambda-powertools/parameters": "npm:^2.14.0"
197197
"@aws-sdk/client-ec2": "npm:^3.749.0"
198198
"@aws-sdk/client-sqs": "npm:^3.749.0"
199199
"@aws-sdk/types": "npm:^3.734.0"
@@ -326,47 +326,47 @@ __metadata:
326326
languageName: unknown
327327
linkType: soft
328328

329-
"@aws-lambda-powertools/commons@npm:^2.13.1":
330-
version: 2.13.1
331-
resolution: "@aws-lambda-powertools/commons@npm:2.13.1"
332-
checksum: 10c0/5a69d4bb3c1d8e9109f9ebac2a91b1b933138edbd62b6141f31b69b85e240871aac734d98ce2f73cfa9267fd59bacc5139470bcbc695433598ade2e187fe23f5
329+
"@aws-lambda-powertools/commons@npm:^2.14.0":
330+
version: 2.14.0
331+
resolution: "@aws-lambda-powertools/commons@npm:2.14.0"
332+
checksum: 10c0/18f2bae4566dee3633de6413cb1053ecc08dbfc8bd4890b8c0b2c0ef6877a1a32665f4f08f6cf3d9ba35f336fb6c90fee601f5986fee96c4f15d99fe0260f688
333333
languageName: node
334334
linkType: hard
335335

336-
"@aws-lambda-powertools/logger@npm:^2.13.1":
337-
version: 2.13.1
338-
resolution: "@aws-lambda-powertools/logger@npm:2.13.1"
336+
"@aws-lambda-powertools/logger@npm:^2.14.0":
337+
version: 2.14.0
338+
resolution: "@aws-lambda-powertools/logger@npm:2.14.0"
339339
dependencies:
340-
"@aws-lambda-powertools/commons": "npm:^2.13.1"
340+
"@aws-lambda-powertools/commons": "npm:^2.14.0"
341341
lodash.merge: "npm:^4.6.2"
342342
peerDependencies:
343343
"@middy/core": 4.x || 5.x || 6.x
344344
peerDependenciesMeta:
345345
"@middy/core":
346346
optional: true
347-
checksum: 10c0/459adef0de50248d6e97e27335a4bb07b611da812942ce0a4091d1802efe3babb64f5a27f4aad41d90fc028afe7cb99462912b9a2d9b39c7ec8400e86e66619f
347+
checksum: 10c0/8a55bcbf64f1d05bf378f3ea08c6010562a29eaa32641c72cddc98cef4d0bb6e6ce25942f2640a4df926c81dbce84082fba98f76a498626232e8157a151c7041
348348
languageName: node
349349
linkType: hard
350350

351-
"@aws-lambda-powertools/metrics@npm:^2.13.1":
352-
version: 2.13.1
353-
resolution: "@aws-lambda-powertools/metrics@npm:2.13.1"
351+
"@aws-lambda-powertools/metrics@npm:^2.14.0":
352+
version: 2.14.0
353+
resolution: "@aws-lambda-powertools/metrics@npm:2.14.0"
354354
dependencies:
355-
"@aws-lambda-powertools/commons": "npm:^2.13.1"
355+
"@aws-lambda-powertools/commons": "npm:^2.14.0"
356356
peerDependencies:
357357
"@middy/core": 4.x || 5.x || 6.x
358358
peerDependenciesMeta:
359359
"@middy/core":
360360
optional: true
361-
checksum: 10c0/e629610a47edac881f1cfdde94ae6b036547abece0878027663ded27405586692e6ca60565f9b45123a80cd6adee28e3c568fd787deacacf071f43821980deed
361+
checksum: 10c0/35eb4a619ab4a2306d01e6cab80b6fe2740a279acfdfe7bd43c57a9db258d3f92318af5d689a738d226f222211dfd8e9779576e29a3496d9201760ef3af3be16
362362
languageName: node
363363
linkType: hard
364364

365-
"@aws-lambda-powertools/parameters@npm:^2.13.1":
366-
version: 2.13.1
367-
resolution: "@aws-lambda-powertools/parameters@npm:2.13.1"
365+
"@aws-lambda-powertools/parameters@npm:^2.14.0":
366+
version: 2.14.0
367+
resolution: "@aws-lambda-powertools/parameters@npm:2.14.0"
368368
dependencies:
369-
"@aws-lambda-powertools/commons": "npm:^2.13.1"
369+
"@aws-lambda-powertools/commons": "npm:^2.14.0"
370370
peerDependencies:
371371
"@aws-sdk/client-appconfigdata": ">=3.x"
372372
"@aws-sdk/client-dynamodb": ">=3.x"
@@ -387,22 +387,22 @@ __metadata:
387387
optional: true
388388
"@middy/core":
389389
optional: true
390-
checksum: 10c0/06ec18cf808585fdfb2f5b06f8134d370764d5f54884a5261666cdd14ac3981faf910e2f1f3b4dc6fc09dc5e56d3146b4018dd0979ba8f5a6ef6e3836ee422a0
390+
checksum: 10c0/50dd302b133721755ad6a96b01c59a48218ff14701c2bf93497d5d69604d9ce1787d16dddacca717428394dcb10e11115fff582a2a392bcb393c6f1229331a77
391391
languageName: node
392392
linkType: hard
393393

394-
"@aws-lambda-powertools/tracer@npm:^2.13.1":
395-
version: 2.13.1
396-
resolution: "@aws-lambda-powertools/tracer@npm:2.13.1"
394+
"@aws-lambda-powertools/tracer@npm:^2.14.0":
395+
version: 2.14.0
396+
resolution: "@aws-lambda-powertools/tracer@npm:2.14.0"
397397
dependencies:
398-
"@aws-lambda-powertools/commons": "npm:^2.13.1"
399-
aws-xray-sdk-core: "npm:^3.10.2"
398+
"@aws-lambda-powertools/commons": "npm:^2.14.0"
399+
aws-xray-sdk-core: "npm:^3.10.3"
400400
peerDependencies:
401401
"@middy/core": 4.x || 5.x || 6.x
402402
peerDependenciesMeta:
403403
"@middy/core":
404404
optional: true
405-
checksum: 10c0/349abfe69ba03f68064f05f9f410b1e726722e64c76b9d6127c7488c0b50f403f0db131ec649a1648b342f0edfbe2732d01fa09315e4ba4361843632acb61005
405+
checksum: 10c0/4b93357bcb118c6f3c1cacd672e4ad7ab95376aa1f89cbe394b6c5aeff1603ca155d1bfa93b2c2d98a42f64f2e4083f936a71a443ae7308c454d65ff8d924439
406406
languageName: node
407407
linkType: hard
408408

@@ -5916,17 +5916,17 @@ __metadata:
59165916
languageName: node
59175917
linkType: hard
59185918

5919-
"aws-xray-sdk-core@npm:^3.10.2":
5920-
version: 3.10.2
5921-
resolution: "aws-xray-sdk-core@npm:3.10.2"
5919+
"aws-xray-sdk-core@npm:^3.10.3":
5920+
version: 3.10.3
5921+
resolution: "aws-xray-sdk-core@npm:3.10.3"
59225922
dependencies:
59235923
"@aws-sdk/types": "npm:^3.4.1"
59245924
"@smithy/service-error-classification": "npm:^2.0.4"
59255925
"@types/cls-hooked": "npm:^4.3.3"
59265926
atomic-batcher: "npm:^1.0.2"
59275927
cls-hooked: "npm:^4.2.2"
59285928
semver: "npm:^7.5.3"
5929-
checksum: 10c0/0d47b13687f841092e927c919085d0570aca67ad9a12251f1d8395c9628f6fcc738d962897032b993c3cf1a94e11cdbe64d23cfbd6106adde732bb46495d5c9e
5929+
checksum: 10c0/8eefc4acca6c230f5ea7219b9671a22d1356a66ad145709b6af07a64f34eb0450a8cd0aaa9fac038163e23f024aaf911b38c46745dbe0fd6f5472ba686584f59
59305930
languageName: node
59315931
linkType: hard
59325932

0 commit comments

Comments
 (0)