Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Bump @aws-lambda-powertools/logger from 1.14.2 to 1.15.0 (#340)
Bumps [@aws-lambda-powertools/logger](https://github.com/aws-powertools/powertools-lambda-typescript) from 1.14.2 to 1.15.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>v1.15.0</h2> <h2>Summary</h2> <p>This release brings support for the new Node.js 20 AWS Lambda managed runtime as well as tweaking how the Metrics utility emits logs under the hood.</p> <h3>Node.js 20 support</h3> <p>With this release we are excited to announce that Powertools for AWS Lambda (TypeScript) is compatible with the <code>nodejs20.x</code> AWS Lambda managed runtime 🎉.</p> <p>The toolkit and our public <a href="https://docs.powertools.aws.dev/lambda/typescript/latest/#lambda-layer">Lambda Layers</a> are both compatible with the new runtime and no code change should be required on your part.</p> <h3>Metrics</h3> <p>The Metrics utility emits logs using the Embedded Metric Format (EMF). Prior to this release, the logs were emitted using the global <code>console</code> object. This makes it so that in addition to the payload of the log, AWS Lambda adds the request id and timestamp of the log.</p> <p>For most customers, and especially those who consume the metrics in Amazon CloudWatch, this is fine as CloudWatch is able to parse the EMF content and create custom metrics. For customers who instead want to send the metrics to third party observability providers the presence of these strings means having an extra parsing step.</p> <p>To support these use cases, and to align with the behavior of the Logger utility, the Metrics utility now uses a dedicated instance of the <code>Console</code> object, which allows it to emit only the content of EMF metric. Just like for the Logger, this behavior can be reverted for development environments by setting the <code>POWERTOOLS_DEV</code> environment variable to a truthy value (i.e. <code>true</code>, <code>yes</code>, <code>1</code>, <code>on</code>, etc.).</p> <p>When <code>POWERTOOLS_DEV</code> is enabled, the Metrics utility reverts to using the global <code>console</code> object. This allows customers to place mock and spies and optionally override the implementation for testing purposes.</p> <h2>Changes</h2> <h2>🌟New features and non-breaking changes</h2> <ul> <li>feat(maintenance): add support for nodejs20.x runtime (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/1790">#1790</a>) by <a href="https://github.com/dreamorosi"><code>@dreamorosi</code></a></li> <li>feat(metrics): log directly to stdout (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/1786">#1786</a>) by <a href="https://github.com/dreamorosi"><code>@dreamorosi</code></a></li> </ul> <h2>🔧 Maintenance</h2> <ul> <li>feat(maintenance): add support for nodejs20.x runtime (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/1790">#1790</a>) by <a href="https://github.com/dreamorosi"><code>@dreamorosi</code></a></li> </ul> <h2>This release was made possible by the following contributors:</h2> <p><a href="https://github.com/dreamorosi"><code>@dreamorosi</code></a></p> </blockquote> </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/v1.14.2...v1.15.0">1.15.0</a> (2023-11-14)</h1> <h3>Features</h3> <ul> <li><strong>maintenance:</strong> add support for nodejs20.x runtime (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/1790">#1790</a>) (<a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/6b9b1bcb9baf4b3d8e0e5ec6709594aca09bb033">6b9b1bc</a>)</li> <li><strong>metrics:</strong> log directly to stdout (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/1786">#1786</a>) (<a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/75dc5b1e16944416a287628c50ec4a0cf82c3023">75dc5b1</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/d508078530fa69b9ab92b203d8a7ccf88e5469a0"><code>d508078</code></a> chore(release): v1.15.0 [skip ci]</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/6b9b1bcb9baf4b3d8e0e5ec6709594aca09bb033"><code>6b9b1bc</code></a> feat(maintenance): add support for nodejs20.x runtime (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/1790">#1790</a>)</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/75dc5b1e16944416a287628c50ec4a0cf82c3023"><code>75dc5b1</code></a> feat(metrics): log directly to stdout (<a href="https://redirect.github.com/aws-powertools/powertools-lambda-typescript/issues/1786">#1786</a>)</li> <li><a href="https://github.com/aws-powertools/powertools-lambda-typescript/commit/73a56cc61ab3c12faaedf888362136a9dd34a843"><code>73a56cc</code></a> chore: update layer ARN on documentation</li> <li>See full diff in <a href="https://github.com/aws-powertools/powertools-lambda-typescript/compare/v1.14.2...v1.15.0">compare view</a></li> </ul> </details> <br /> [](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>
- Loading branch information
1 parent
331441f
commit b4579f3