8000 chore(deps): bump the npm-dependencies-root group with 5 updates by dependabot[bot] · Pull Request #149 · andmoredev/layerless-esbuild-lambda · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

chore(deps): bump the npm-dependencies-root group with 5 updates #149

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
Merged
merged 1 commit into from
Jun 4, 2025
Merged

chore(deps): bump the npm-dependencies-root group with 5 updates #149

merged 1 commit into from
Jun 4, 2025

Conversation

dependabot[bot]
Copy link
Contributor
@dependabot dependabot bot commented on behalf of github Jun 4, 2025

Bumps the npm-dependencies-root group with 5 updates:

Package From To
@aws-lambda-powertools/logger 2.20.0 2.21.0
@aws-lambda-powertools/metrics 2.20.0 2.21.0
@aws-lambda-powertools/parameters 2.20.0 2.21.0
@aws-lambda-powertools/tracer 2.20.0 2.21.0
@aws-sdk/client-secrets-manager 3.821.0 3.823.0

Updates @aws-lambda-powertools/logger from 2.20.0 to 2.21.0

Release notes

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

v2.21.0

Summary

This release introduces a new BedrockAgentFunctionResolver to Event Handler that simplifies connecting AWS Lambda functions to Amazon Bedrock Agents. This feature eliminates the need to write boilerplate code for parsing requests and formatting responses, allowing you to focus on your agent's business logic.

⭐ A big thank you to @​VatsalGoel3 and @​svozza for their contributions to this release and to Instil for becoming a public customer reference!

Creating Amazon Bedrock Agents

Docs

You can now use the new BedrockAgentFunctionResolver to register tools and handle requests in your Lambda functions. The resolver will automatically parse the request, route it to the appropriate function, and return a well-formed response that includes the tool's output and any existing session attributes.

carbon

By default, errors are handled gracefully and returned to the agent with error type and message information, allowing the conversation to continue. This is useful when you want to let the LLM handle errors and reduce boilerplate error-handling code.

If you need more control over error scenarios, you can use BedrockFunctionResponse to customize the response and determine if the conversation should continue:

carbon

You can also use the BedrockFunctionResponse when you want to enrich the response with session attributes or knowledge base configurations, or when you want the agent to re-prompt the user to provide additional information.

carbon-2

Changes

🌟New features and non-breaking changes

📜 Documentation updates

... (truncated)

Changelog

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

2.21.0 (2025-06-03)

Bug Fixes

  • parameters: preserve original stack trace on transform failures … (#3982) (583e3ae)

Features

  • commons: environment variable helpers (#3945) (7cfcd85)
  • event-handler: add Amazon Bedrock Agents Functions Resolver (#3957) (720ddcb)
Commits
  • d3e4184 chore(ci): bump version to 2.21.0 (#4005)
  • 7361e11 docs(event-handler): add docs page for Bedrock Agent Function (#3991)
  • 583e3ae fix(parameters): preserve original stack trace on transform failures … (#3982)
  • 3c38308 chore(deps): bump the aws-cdk group across 1 directory with 3 updates (#4004)
  • de07c06 chore(deps-dev): bump lint-staged from 16.0.0 to 16.1.0 (#3994)
  • 35c496f chore(deps): bump @​types/node from 22.15.23 to 22.15.29 (#4001)
  • 2b0ec42 chore(deps): bump the aws-sdk-v3 group across 1 directory with 9 updates (#4002)
  • fe1b5c3 chore(deps): bump ossf/scorecard-action from 2.4.1 to 2.4.2 (#4003)
  • de170ba chore(deps-dev): bump zod from 3.25.32 to 3.25.48 (#4000)
  • 2870ee8 chore(deps): bump vscode/devcontainers/javascript-node from 1ab856e to `0d2...
  • Additional commits viewable in compare view

Updates @aws-lambda-powertools/metrics from 2.20.0 to 2.21.0

Release notes

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

v2.21.0

Summary

This release introduces a new BedrockAgentFunctionResolver to Event Handler that simplifies connecting AWS Lambda functions to Amazon Bedrock Agents. This feature eliminates the need to write boilerplate code for parsing requests and formatting responses, allowing you to focus on your agent's business logic.

⭐ A big thank you to @​VatsalGoel3 and @​svozza for their contributions to this release and to Instil for becoming a public customer reference!

Creating Amazon Bedrock Agents

Docs

You can now use the new BedrockAgentFunctionResolver to register tools and handle requests in your Lambda functions. The resolver will automatically parse the request, route it to the appropriate function, and return a well-formed response that includes the tool's output and any existing session attributes.

carbon

By default, errors are handled gracefully and returned to the agent with error type and message information, allowing the conversation to continue. This is useful when you want to let the LLM handle errors and reduce boilerplate error-handling code.

If you need more control over error scenarios, you can use BedrockFunctionResponse to customize the response and determine if the conversation should continue:

carbon

You can also use the BedrockFunctionResponse when you want to enrich the response with session attributes or knowledge base configurations, or when you want the agent to re-prompt the user to provide additional information.

carbon-2

Changes

🌟New features and non-breaking changes

📜 Documentation updates

... (truncated)

Changelog

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

2.21.0 (2025-06-03)

Bug Fixes

  • parameters: preserve original stack trace on transform failures … (#3982) (583e3ae)

Features

  • commons: environment variable helpers (#3945) (7cfcd85)
  • event-handler: add Amazon Bedrock Agents Functions Resolver (#3957) (720ddcb)
Commits
  • d3e4184 chore(ci): bump version to 2.21.0 (#4005)
  • 7361e11 docs(event-handler): add docs page for Bedrock Agent Function (#3991)
  • 583e3ae fix(parameters): preserve original stack trace on transform failures … (#3982)
  • 3c38308 chore(deps): bump the aws-cdk group across 1 directory with 3 updates (#4004)
  • de07c06 chore(deps-dev): bump lint-staged from 16.0.0 to 16.1.0 (#3994)
  • 35c496f chore(deps): bump @​types/node from 22.15.23 to 22.15.29 (#4001)
  • 2b0ec42 chore(deps): bump the aws-sdk-v3 group across 1 directory with 9 updates (#4002)
  • fe1b5c3 chore(deps): bump ossf/scorecard-action from 2.4.1 to 2.4.2 (#4003)
  • de170ba chore(deps-dev): bump zod from 3.25.32 to 3.25.48 (#4000)
  • 2870ee8 chore(deps): bump vscode/devcontainers/javascript-node from 1ab856e to `0d2...
  • Additional commits viewable in compare view

Updates @aws-lambda-powertools/parameters from 2.20.0 to 2.21.0

Release notes

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

v2.21.0

Summary

This release introduces a new BedrockAgentFunctionResolver to Event Handler that simplifies connecting AWS Lambda functions to Amazon Bedrock Agents. This feature eliminates the need to write boilerplate code for parsing requests and formatting responses, allowing you to focus on your agent's business logic.

⭐ A big thank you to @​VatsalGoel3 and @​svozza for their contributions to this release and to Instil for becoming a public customer reference!

Creating Amazon Bedrock Agents

Docs

You can now use the new BedrockAgentFunctionResolver to register tools and handle requests in your Lambda functions. The resolver will automatically parse the request, route it to the appropriate function, and return a well-formed response that includes the tool's output and any existing session attributes.

carbon

By default, errors are handled gracefully and returned to the agent with error type and message information, allowing the conversation to continue. This is useful when you want to let the LLM handle errors and reduce boilerplate error-handling code.

If you need more control over error scenarios, you can use BedrockFunctionResponse to customize the response and determine if the conversation should continue:

carbon

You can also use the BedrockFunctionResponse when you want to enrich the response with session attributes or knowledge base configurations, or when you want the agent to re-prompt the user to provide additional information.

carbon-2

Changes

🌟New features and non-breaking changes

📜 Documentation updates

... (truncated)

Changelog

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

2.21.0 (2025-06-03)

Bug Fixes

  • parameters: preserve original stack trace on transform failures … (#3982) (583e3ae)

Features

  • commons: environment variable helpers (#3945) (7cfcd85)
  • event-handler: add Amazon Bedrock Agents Functions Resolver (#3957) (720ddcb)
Commits
  • d3e4184 chore(ci): bump version to 2.21.0 (#4005)
  • 7361e11 docs(event-handler): add docs page for Bedrock Agent Function (#3991)
  • 583e3ae fix(parameters): preserve original stack trace on transform failures … (#3982)
  • 3c38308 chore(deps): bump the aws-cdk group across 1 directory with 3 updates (#4004)
  • de07c06 chore(deps-dev): bump lint-staged from 16.0.0 to 16.1.0 (#3994)
  • 35c496f chore(deps): bump @​types/node from 22.15.23 to 22.15.29 (#4001)
  • 2b0ec42 chore(deps): bump the aws-sdk-v3 group across 1 directory with 9 updates (#4002)
  • fe1b5c3 chore(deps): bump ossf/scorecard-action from 2.4.1 to 2.4.2 (#4003)
  • de170ba chore(deps-dev): bump zod from 3.25.32 to 3.25.48 (#4000)
  • 2870ee8 chore(deps): bump vscode/devcontainers/javascript-node from 1ab856e to `0d2...
  • Additional commits viewable in compare view

Updates @aws-lambda-powertools/tracer from 2.20.0 to 2.21.0

Release notes

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

v2.21.0

Summary

This release introduces a new BedrockAgentFunctionResolver to Event Handler that simplifies connecting AWS Lambda functions to Amazon Bedrock Agents. This feature eliminates the need to write boilerplate code for parsing requests and formatting responses, allowing you to focus on your agent's business logic.

⭐ A big thank you to @​VatsalGoel3 and @​svozza for their contributions to this release and to Instil for becoming a public customer reference!

Creating Amazon Bedrock Agents

Docs

You can now use the new BedrockAgentFunctionResolver to register tools and handle requests in your Lambda functions. The resolver will automatically parse the request, route it to the appropriate function, and return a well-formed response that includes the tool's output and any existing session attributes.

carbon

By default, errors are handled gracefully and returned to the agent with error type and message information, allowing the conversation to continue. This is useful when you want to let the LLM handle errors and reduce boilerplate error-handling code.

If you need more control over error scenarios, you can use BedrockFunctionResponse to customize the response and determine if the conversation should continue:

carbon

You can also use the BedrockFunctionResponse when you want to enrich the response with session attributes or knowledge base configurations, or when you want the agent to re-prompt the user to provide additional information.

carbon-2

Changes

🌟New features and non-breaking changes

📜 Documentation updates

... (truncated)

Changelog

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

2.21.0 (2025-06-03)

Bug Fixes

  • parameters: preserve original stack trace on transform failures … (#3982) (583e3ae)

Features

  • commons: environment variable helpers (#3945) (7cfcd85)
  • event-handler: add Amazon Bedrock Agents Functions Resolver (#3957) (720ddcb)
Commits
  • d3e4184 chore(ci): bump version to 2.21.0 (#4005)
  • 7361e11 docs(event-handler): add docs page for Bedrock Agent Function (#3991)
  • 583e3ae fix(parameters): preserve original stack trace on transform failures … (#3982)
  • 3c38308 chore(deps): bump the aws-cdk group across 1 directory with 3 updates (#4004)
  • de07c06 chore(deps-dev): bump lint-staged from 16.0.0 to 16.1.0 (#3994)
  • 35c496f chore(deps): bump @​types/node from 22.15.23 to 22.15.29 (#4001)
  • 2b0ec42 chore(deps): bump the aws-sdk-v3 group across 1 directory with 9 updates (#4002)
  • fe1b5c3 chore(deps): bump ossf/scorecard-action from 2.4.1 to 2.4.2 (#4003)
  • de170ba chore(deps-dev): bump zod from 3.25.32 to 3.25.48 (#4000)
  • 2870ee8 chore(deps): bump vscode/devcontainers/javascript-node from 1ab856e to `0d2...
  • Additional commits viewable in compare view

Updates @aws-sdk/client-secrets-manager from 3.821.0 to 3.823.0

Release notes

Sourced from @​aws-sdk/client-secrets-manager's releases.

v3.823.0

3.823.0(2025-06-03)

New Features
  • client-apigatewayv2: Adds support to create routing rules and set the routing mode for a custom domain name. (adc341a7)
  • client-emr-serverless: AWS EMR Serverless: Adds a new option in the CancelJobRun API in EMR 7.9.0+, to cancel a job with grace period. This feature is enabled by default with a 120-second grace period for streaming jobs and is not enabled by default for batch jobs. (a04fee3c)
  • client-api-gateway: Adds support to set the routing mode for a custom domain name. (fa3d7b94)
  • core/protocols: runtime protocol classes (#7110) (9babfac3)

For list of updated packages, view updated-packages.md in assets-3.823.0.zip

v3.822.0

3.822.0(2025-06-02)

Documentation Changes
  • client-ecs: Updates Amazon ECS documentation to include note for upcoming default log driver mode change. (195b6221)
New Features
  • clients: update client endpoints as of 2025-06-02 (c61981ff)
  • client-cost-optimization-hub: Support recommendations for Aurora instance and Aurora cluster storage. (307d369a)
  • client-athena: Add support for the managed query result in the workgroup APIs. The managed query result configuration enables users to store query results to Athena owned storage. (33fac0af)
  • client-backup: You can now subscribe to Amazon SNS notifications and Amazon EventBridge events for backup indexing. You can now receive notifications when a backup index is created, deleted, or fails to create, enhancing your ability to monitor and track your backup operations. (9bec4efa)
  • client-entityresolution: Add support for generating match IDs in near real-time. (697753c2)
  • client-eks: Add support for filtering ListInsights API calls on MISCONFIGURATION insight category (88f26232)
  • client-synthetics: Support for Java runtime handler pattern. (ee418d1f)
  • client-bedrock-agent: This release adds the Agent Lifecycle Paused State feature to Amazon Bedrock agents. By using an agent's alias, you can temporarily suspend agent operations during maintenance, updates, or other situations. (26fec880)
  • client-compute-optimizer: This release enables AWS Compute Optimizer to analyze Amazon Aurora database clusters and generate Aurora I/O-Optimized recommendations. (a741c9e2)
  • client-pcs: Introduces SUSPENDING and SUSPENDED states for clusters, compute node groups, and queues. (172256cc)

For list of updated packages, view update 8000 d-packages.md in assets-3.822.0.zip

Changelog

Sourced from @​aws-sdk/client-secrets-manager's changelog.

3.823.0 (2025-06-03)

Note: Version bump only for package @​aws-sdk/client-secrets-manager

Commits

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
chore(deps): bump the npm-dependencies-root group with 5 updates
98ad633 
Bumps the npm-dependencies-root group with 5 updates:

| Package | From | To |
| --- | --- | --- |
| [@aws-lambda-powertools/logger](https://github.com/aws-powertools/powertools-lambda-typescript) | `2.20.0` | `2.21.0` |
| [@aws-lambda-powertools/metrics](https://github.com/aws-powertools/powertools-lambda-typescript) | `2.20.0` | `2.21.0` |
| [@aws-lambda-powertools/parameters](https://github.com/aws-powertools/powertools-lambda-typescript) | `2.20.0` | `2.21.0` |
| [@aws-lambda-powertools/tracer](https://github.com/aws-powertools/powertools-lambda-typescript) | `2.20.0` | `2.21.0` |
| [@aws-sdk/client-secrets-manager](https://github.com/aws/aws-sdk-js-v3/tree/HEAD/clients/client-secrets-manager) | `3.821.0` | `3.823.0` |


Updates `@aws-lambda-powertools/logger` from 2.20.0 to 2.21.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.20.0...v2.21.0)

Updates `@aws-lambda-powertools/metrics` from 2.20.0 to 2.21.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.20.0...v2.21.0)

Updates `@aws-lambda-powertools/parameters` from 2.20.0 to 2.21.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.20.0...v2.21.0)

Updates `@aws-lambda-powertools/tracer` from 2.20.0 to 2.21.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.20.0...v2.21.0)

Updates `@aws-sdk/client-secrets-manager` from 3.821.0 to 3.823.0
- [Release notes](https://github.com/aws/aws-sdk-js-v3/releases)
- [Changelog](https://github.com/aws/aws-sdk-js-v3/blob/main/clients/client-secrets-manager/CHANGELOG.md)
- [Commits](https://github.com/aws/aws-sdk-js-v3/commits/v3.823.0/clients/client-secrets-manager)

---
updated-dependencies:
- dependency-name: "@aws-lambda-powertools/logger"
  dependency-version: 2.21.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-dependencies-root
- dependency-name: "@aws-lambda-powertools/metrics"
  dependency-version: 2.21.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-dependencies-root
- dependency-name: "@aws-lambda-powertools/parameters"
  dependency-version: 2.21.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-dependencies-root
- dependency-name: "@aws-lambda-powertools/tracer"
  dependency-version: 2.21.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-dependencies-root
- dependency-name: "@aws-sdk/client-secrets-manager"
  dependency-version: 3.823.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-dependencies-root
...

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 Jun 4, 2025
@sonarqubecloud SonarQubeCloud
Copy link
sonarqubecloud bot commented Jun 4, 2025

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

@github-actions github-actions bot merged commit c4432e7 into main Jun 4, 2025
10 checks passed
@github-actions github-actions bot deleted the dependabot/npm_and_yarn/npm-dependencies-root-c91b242ac0 branch June 4, 2025 04:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@github-actions github-actions[bot] github-actions[bot] approved these changes

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.
0 participants
0