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.

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

Update aws-sdk-js-v3 monorepo to v3.705.0 #2668

Open
wants to merge 1 commit into
base: trunk
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 5, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@aws-sdk/client-dynamodb (source) 3.699.0 -> 3.705.0 age adoption passing confidence
@aws-sdk/client-s3 (source) 3.701.0 -> 3.705.0 age adoption passing confidence
@aws-sdk/util-dynamodb (source) 3.699.0 -> 3.705.0 age adoption passing confidence

Release Notes

aws/aws-sdk-js-v3 (@​aws-sdk/client-dynamodb)

v3.705.0

Compare Source

Features
  • client-dynamodb: This change adds support for global tables with multi-Region strong consistency (in preview). The UpdateTable API now supports a new attribute MultiRegionConsistency to set consistency when creating global tables. The DescribeTable output now optionally includes the MultiRegionConsistency attribute. (c96da51)
aws/aws-sdk-js-v3 (@​aws-sdk/client-s3)

v3.705.0

Compare Source

Features
  • client-s3: Amazon S3 Metadata stores object metadata in read-only, fully managed Apache Iceberg metadata tables that you can query. You can create metadata table configurations for S3 general purpose buckets. (b6368e5)

v3.703.0

Compare Source

Features
  • client-s3: Amazon S3 introduces support for AWS Dedicated Local Zones (a4b4303)
aws/aws-sdk-js-v3 (@​aws-sdk/util-dynamodb)

v3.705.0

Compare Source

Note: Version bump only for package @​aws-sdk/util-dynamodb

v3.704.0

Compare Source

Note: Version bump only for package @​aws-sdk/util-dynamodb


Configuration

📅 Schedule: Branch creation - "* * * * 1-5" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/aws-sdk-js-v3-monorepo branch from 0bcae19 to 4d6e82e Compare December 6, 2024 07:58
@renovate renovate bot changed the title fix(deps): update dependency @aws-sdk/client-s3 to v3.703.0 fix(deps): update aws-sdk-js-v3 monorepo Dec 6, 2024
@renovate renovate bot force-pushed the renovate/aws-sdk-js-v3-monorepo branch from 4d6e82e to 1891032 Compare December 6, 2024 22:24
@renovate renovate bot changed the title fix(deps): update aws-sdk-js-v3 monorepo fix(deps): update aws-sdk-js-v3 monorepo to v3.705.0 Dec 6, 2024
@renovate renovate bot changed the title fix(deps): update aws-sdk-js-v3 monorepo to v3.705.0 fix(deps): update aws-sdk-js-v3 monorepo to v3.705.0 - autoclosed Dec 8, 2024
@renovate renovate bot closed this Dec 8, 2024
@renovate renovate bot deleted the renovate/aws-sdk-js-v3-monorepo branch December 8, 2024 18:53
@renovate renovate bot changed the title fix(deps): update aws-sdk-js-v3 monorepo to v3.705.0 - autoclosed fix(deps): update aws-sdk-js-v3 monorepo to v3.705.0 Dec 9, 2024
@renovate renovate bot reopened this Dec 9, 2024
@renovate renovate bot force-pushed the renovate/aws-sdk-js-v3-monorepo branch 2 times, most recently from 1891032 to cdc6b64 Compare December 9, 2024 16:02
@renovate renovate bot changed the title fix(deps): update aws-sdk-js-v3 monorepo to v3.705.0 Update aws-sdk-js-v3 monorepo to v3.705.0 Dec 9, 2024
@renovate renovate bot force-pushed the renovate/aws-sdk-js-v3-monorepo branch from cdc6b64 to 97c569e Compare December 9, 2024 18:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants