Upgrade: [dependabot] - bump @aws-lambda-powertools/logger from 2.13.…

…1 to 2.14.0 (#336)

Bumps
[@aws-lambda-powertools/logger](https://github.com/aws-powertools/powertools-lambda-typescript)
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 />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=@aws-lambda-powertools/logger&package-manager=npm_and_yarn&previous-version=2.13.1&new-version=2.14.0)](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)

---

<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 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)


</details>

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

package.json

@@ -38,7 +38,7 @@
     "typescript": "^5.7.3"
   },
   "dependencies": {
-    "@aws-lambda-powertools/logger": "^2.13.1",
+    "@aws-lambda-powertools/logger": "^2.14.0",
     "@types/mustache": "^4.2.5",
     "aws-lambda": "^1.0.7",
     "axios": "^1.7.9",