Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Merged
merged 1 commit into from
Oct 17, 2024
Merged

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

merged 1 commit into from
Oct 17, 2024
+37 −37

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 14, 2024

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.8.0 to 2.9.0

Release notes

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

v2.9.0

Summary

This release introduces 1/ the ability to process records sequentially when working with async functions in Batch Processing, 2/ a new option for Idempotency to manipulate the payload stored for idempotent operations, and 3/ the option to specify custom JMESPath functions when selecting an idempotency key.

Finally, you can now use the Parser utility when using our public AWS Lambda layers.

⭐️ Thanks to @​arnabrahman, @​garysassano and, @​scratchclaggy for their big contributions to this release!

Sequential async processing

Docs

You can now process records sequentially when working with async functions in Batch Processing by setting the processInParallel option to false. This is useful for when you want to opt-out of the default behavior and preserve the order of the records.

carbon-4

Manipulating idempotent responses

Docs

Now you can set up a responseHook function when configuring the Idempotency utility to manipulate the returned data when an operation is idempotent.

carbon-3

Custom JMESPath functions with Idempotency

Docs

You can now use custom JMESPath functions with the Idempotency utility by configuring the jmesPathOptions in your idempotency configuration. This is useful when you’re making idempotent operations that accept complex payloads or encoding formats that are not supported by default.

carbon-4

Changes

🌟New features and non-breaking changes

... (truncated)

Changelog

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

2.9.0 (2024-10-07)

Features

  • batch: sequential async processing of records for BatchProcessor (#3109) (e31279a)
  • idempotency: ability to specify JMESPath custom functions (#3150) (869b6fc)
  • idempotency: manipulate idempotent response via response hook (#3071) (f7c1769)
Commits
  • 71e70f5 chore(ci): bump version to 2.9.0 (#3164)
  • 74c6edd chore(deps): bump the aws-cdk group across 1 directory with 2 updates (#3163)
  • 613d32c chore(deps): bump zgosalvez/github-actions-ensure-sha-pinned-actions from 3.0...
  • 39b805b chore(deps): bump the aws-sdk-v3 group across 1 directory with 9 updates (#3156)
  • 7be70a1 chore(deps): bump github/codeql-action from 3.26.9 to 3.26.11 (#3157)
  • 489c8ad chore(maintenance): add Flyweight customer reference (#3161)
  • 0c44517 docs(parser): highlight JSONStringify helper (#3158)
  • 869b6fc feat(idempotency): ability to specify JMESPath custom functions (#3150)
  • 686e524 chore(metrics): expose MetricsInterface as return type of single metric and...
  • c97d379 test(idempotency): switch e2e tests to vitest (#3149)
  • Additional commits viewable in compare view

Updates @aws-lambda-powertools/logger from 2.8.0 to 2.9.0

Release notes

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

v2.9.0

Summary

This release introduces 1/ the ability to process records sequentially when working with async functions in Batch Processing, 2/ a new option for Idempotency to manipulate the payload stored for idempotent operations, and 3/ the option to specify custom JMESPath functions when selecting an idempotency key.

Finally, you can now use the Parser utility when using our public AWS Lambda layers.

⭐️ Thanks to @​arnabrahman, @​garysassano and, @​scratchclaggy for their big contributions to this release!

Sequential async processing

Docs

You can now process records sequentially when working with async functions in Batch Processing by setting the processInParallel option to false. This is useful for when you want to opt-out of the default behavior and preserve the order of the records.

carbon-4

Manipulating idempotent responses

Docs

Now you can set up a responseHook function when configuring the Idempotency utility to manipulate the returned data when an operation is idempotent.

carbon-3

Custom JMESPath functions with Idempotency

Docs

You can now use custom JMESPath functions with the Idempotency utility by configuring the jmesPathOptions in your idempotency configuration. This is useful when you’re making idempotent operations that accept complex payloads or encoding formats that are not supported by default.

carbon-4

Changes

🌟New features and non-breaking changes

... (truncated)

Changelog

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

2.9.0 (2024-10-07)

Features

  • batch: sequential async processing of records for BatchProcessor (#3109) (e31279a)
  • idempotency: ability to specify JMESPath custom functions (#3150) (869b6fc)
  • idempotency: manipulate idempotent response via response hook (#3071) (f7c1769)
Commits
  • 71e70f5 chore(ci): bump version to 2.9.0 (#3164)
  • 74c6edd chore(deps): bump the aws-cdk group across 1 directory with 2 updates (#3163)
  • 613d32c chore(deps): bump zgosalvez/github-actions-ensure-sha-pinned-actions from 3.0...
  • 39b805b chore(deps): bump the aws-sdk-v3 group across 1 directory with 9 updates (#3156)
  • 7be70a1 chore(deps): bump github/codeql-action from 3.26.9 to 3.26.11 (#3157)
  • 489c8ad chore(maintenance): add Flyweight customer reference (#3161)
  • 0c44517 docs(parser): highlight JSONStringify helper (#3158)
  • 869b6fc feat(idempotency): ability to specify JMESPath custom functions (#3150)
  • 686e524 chore(metrics): expose MetricsInterface as return type of single metric and...
  • c97d379 test(idempotency): switch e2e tests to vitest (#3149)
  • Additional commits viewable in compare view

Updates @aws-lambda-powertools/metrics from 2.8.0 to 2.9.0

Release notes

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

v2.9.0

Summary

This release introduces 1/ the ability to process records sequentially when working with async functions in Batch Processing, 2/ a new option for Idempotency to manipulate the payload stored for idempotent operations, and 3/ the option to specify custom JMESPath functions when selecting an idempotency key.

Finally, you can now use the Parser utility when using our public AWS Lambda layers.

⭐️ Thanks to @​arnabrahman, @​garysassano and, @​scratchclaggy for their big contributions to this release!

Sequential async processing

Docs

You can now process records sequentially when working with async functions in Batch Processing by setting the processInParallel option to false. This is useful for when you want to opt-out of the default behavior and preserve the order of the records.

carbon-4

Manipulating idempotent responses

Docs

Now you can set up a responseHook function when configuring the Idempotency utility to manipulate the returned data when an operation is idempotent.

carbon-3

Custom JMESPath functions with Idempotency

Docs

You can now use custom JMESPath functions with the Idempotency utility by configuring the jmesPathOptions in your idempotency configuration. This is useful when you’re making idempotent operations that accept complex payloads or encoding formats that are not supported by default.

carbon-4

Changes

🌟New features and non-breaking changes

... (truncated)

Changelog

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

2.9.0 (2024-10-07)

Features

  • batch: sequential async processing of records for BatchProcessor (#3109) (e31279a)
  • idempotency: ability to specify JMESPath custom functions (#3150) (869b6fc)
  • idempotency: manipulate idempotent response via response hook (#3071) (f7c1769)
Commits
  • 71e70f5 chore(ci): bump version to 2.9.0 (#3164)
  • 74c6edd chore(deps): bump the aws-cdk group across 1 directory with 2 updates (#3163)
  • 613d32c chore(deps): bump zgosalvez/github-actions-ensure-sha-pinned-actions from 3.0...
  • 39b805b chore(deps): bump the aws-sdk-v3 group across 1 directory with 9 updates (#3156)
  • 7be70a1 chore(deps): bump github/codeql-action from 3.26.9 to 3.26.11 (#3157)
  • 489c8ad chore(maintenance): add Flyweight customer reference (#3161)
  • 0c44517 docs(parser): highlight JSONStringify helper (#3158)
  • 869b6fc feat(idempotency): ability to specify JMESPath custom functions (#3150)
  • 686e524 chore(metrics): expose MetricsInterface as return type of single metric and...
  • c97d379 test(idempotency): switch e2e tests to vitest (#3149)
  • Additional commits viewable in compare view

Updates @aws-lambda-powertools/tracer from 2.8.0 to 2.9.0

Release notes

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

v2.9.0

Summary

This release introduces 1/ the ability to process records sequentially when working with async functions in Batch Processing, 2/ a new option for Idempotency to manipulate the payload stored for idempotent operations, and 3/ the option to specify custom JMESPath functions when selecting an idempotency key.

Finally, you can now use the Parser utility when using our public AWS Lambda layers.

⭐️ Thanks to @​arnabrahman, @​garysassano and, @​scratchclaggy for their big contributions to this release!

Sequential async processing

Docs

You can now process records sequentially when working with async functions in Batch Processing by setting the processInParallel option to false. This is useful for when you want to opt-out of the default behavior and preserve the order of the records.

carbon-4

Manipulating idempotent responses

Docs

Now you can set up a responseHook function when configuring the Idempotency utility to manipulate the returned data when an operation is idempotent.

carbon-3

Custom JMESPath functions with Idempotency

Docs

You can now use custom JMESPath functions with the Idempotency utility by configuring the jmesPathOptions in your idempotency configuration. This is useful when you’re making idempotent operations that accept complex payloads or encoding formats that are not supported by default.

carbon-4

Changes

🌟New features and non-breaking changes

... (truncated)

Changelog

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

2.9.0 (2024-10-07)

Features

  • batch: sequential async processing of records for BatchProcessor (#3109) (e31279a)
  • idempotency: ability to specify JMESPath custom functions (#3150) (869b6fc)
  • idempotency: manipulate idempotent response via response hook (#3071) (f7c1769)
Commits
  • 71e70f5 chore(ci): bump version to 2.9.0 (#3164)
  • 74c6edd chore(deps): bump the aws-cdk group across 1 directory with 2 updates (#3163)
  • 613d32c chore(deps): bump zgosalvez/github-actions-ensure-sha-pinned-actions from 3.0...
  • 39b805b chore(deps): bump the aws-sdk-v3 group across 1 directory with 9 updates (#3156)
  • 7be70a1 chore(deps): bump github/codeql-action from 3.26.9 to 3.26.11 (#3157)
  • 489c8ad chore(maintenance): add Flyweight customer reference (#3161)
  • 0c44517 docs(parser): highlight JSONStringify helper (#3158)
  • 869b6fc feat(idempotency): ability to specify JMESPath custom functions (#3150)
  • 686e524 chore(metrics): expose MetricsInterface as return type of single metric and...
  • c97d379 test(idempotency): switch e2e tests to vitest (#3149)
  • 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

@dependabot
fix(lambda): bump the aws-powertools group in /lambdas with 4 updates
86c2d25 
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.8.0 to 2.9.0
- [Release notes](https://github.com/aws-powertools/powertools-lambda-typescript/releases)
- [Changelog](https://github.com/aws-powertools/powertools-lambda-typescript/blob/main/CHANGELOG.md)
- [Commits](aws-powertools/powertools-lambda-typescript@v2.8.0...v2.9.0)

Updates `@aws-lambda-powertools/logger` from 2.8.0 to 2.9.0
- [Release notes](https://github.com/aws-powertools/powertools-lambda-typescript/releases)
- [Changelog](https://github.com/aws-powertools/powertools-lambda-typescript/blob/main/CHANGELOG.md)
- [Commits](aws-powertools/powertools-lambda-typescript@v2.8.0...v2.9.0)

Updates `@aws-lambda-powertools/metrics` from 2.8.0 to 2.9.0
- [Release notes](https://github.com/aws-powertools/powertools-lambda-typescript/releases)
- [Changelog](https://github.com/aws-powertools/powertools-lambda-typescript/blob/main/CHANGELOG.md)
- [Commits](aws-powertools/powertools-lambda-typescript@v2.8.0...v2.9.0)

Updates `@aws-lambda-powertools/tracer` from 2.8.0 to 2.9.0
- [Release notes](https://github.com/aws-powertools/powertools-lambda-typescript/releases)
- [Changelog](https://github.com/aws-powertools/powertools-lambda-typescript/blob/main/CHANGELOG.md)
- [Commits](aws-powertools/powertools-lambda-typescript@v2.8.0...v2.9.0)

---
updated-dependencies:
- dependency-name: "@aws-lambda-powertools/parameters"
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: aws-powertools
- dependency-name: "@aws-lambda-powertools/logger"
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: aws-powertools
- dependency-name: "@aws-lambda-powertools/metrics"
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: aws-powertools
- dependency-name: "@aws-lambda-powertools/tracer"
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: aws-powertools
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Oct 14, 2024
@npalm npalm merged commit e18ac60 into main Oct 17, 2024
4 checks passed
@npalm npalm deleted the dependabot/npm_and_yarn/lambdas/aws-powertools-67be884974 branch October 17, 2024 07:22
@forest-releaser forest-releaser bot mentioned this pull request Oct 17, 2024
Merged
npalm pushed a commit that referenced this pull request Oct 17, 2024
@forest-releaser
chore(main): release 5.17.1 (#4190)
4708125 
🤖 I have created a release *beep* *boop*
---


##
[5.17.1](v5.17.0...v5.17.1)
(2024-10-17)


### Bug Fixes

* **lambda:** bump @octokit/types from 13.5.0 to 13.6.1 in /lambdas in
the octokit group
([#4183](#4183))
([f24469f](f24469f))
* **lambda:** bump the aws group across 1 directory with 5 updates
([#4191](#4191))
([bf8a924](bf8a924))
* **lambda:** bump the aws-powertools group in /lambdas with 4 updates
([#4184](#4184))
([e18ac60](e18ac60))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: forest-releaser[bot] <80285352+forest-releaser[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@npalm