Skip to content

refactor: Upgrade @aws-sdk/client-s3 from 3.779.0 to 3.787.0 #261

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

Closed

Conversation

parseplatformorg
Copy link
Contributor

@parseplatformorg parseplatformorg commented May 2, 2025

snyk-top-banner

Snyk has created this PR to upgrade @aws-sdk/client-s3 from 3.779.0 to 3.787.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 2 versions ahead of your current version.

  • The recommended version was released 22 days ago.

Release notes
Package name: @aws-sdk/client-s3
  • 3.787.0 - 2025-04-10

    3.787.0(2025-04-10)

    Chores
    • util-endpoints: update aws partitions.json (cb2a9f29)
    • endpoints: update endpoints model (2874c7d1)
    • models: update API models (8f65fca0)
    • codegen: bring in fix for operationContextParams (#7004) (a7d9c1f9)
    • aws-util-test:
    New Features
    • client-application-auto-scaling: Application Auto Scaling now supports horizontal scaling for Elasticache Memcached self-designed clusters using target tracking scaling policies and scheduled scaling. (38a22fb9)
    • client-qbusiness: Adds functionality to enable/disable a new Q Business Hallucination Reduction feature. If enabled, Q Business will detect and attempt to remove Hallucinations from certain Chat requests. (a7fb9d51)
    • client-elasticache: AWS ElastiCache SDK now supports using MemcachedUpgradeConfig parameter with ModifyCacheCluster API to enable updating Memcached cache node types. Please refer to updated AWS ElastiCache public documentation for detailed information on API usage and implementation. (7be36747)
    • client-m2: Introduce three new APIs: CreateDataSetExportTask, GetDataSetExportTask and ListDataSetExportHistory. Add support for batch restart for Blu Age applications. (2c22fc3e)
    • client-quicksight: Add support to analysis and sheet level highlighting in QuickSight. (fd1d5c3c)
    • client-medialive: AWS Elemental MediaLive / Features : Add support for CMAF Ingest CaptionLanguageMappings, TimedMetadataId3 settings, and Link InputResolution. (4f30f3e3)
    Tests
    • middleware-flexible-checksums: update instructions for MD5 fallback (#7002) (d1501040)

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

  • 3.782.0 - 2025-04-03
  • 3.779.0 - 2025-03-31
from @aws-sdk/client-s3 GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Summary by CodeRabbit

  • Chores
    • Updated the "@aws-sdk/client-s3" dependency to version 3.787.0.

Snyk has created this PR to upgrade @aws-sdk/client-s3 from 3.779.0 to 3.787.0.

See this package in npm:
@aws-sdk/client-s3

See this project in Snyk:
https://app.snyk.io/org/acinader/project/3364151b-9c9a-4458-9afd-809dc5309438?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

I will reformat the title to use the proper commit message syntax.

@parse-github-assistant parse-github-assistant bot changed the title [Snyk] Upgrade @aws-sdk/client-s3 from 3.779.0 to 3.787.0 refactor: Upgrade @aws-sdk/client-s3 from 3.779.0 to 3.787.0 May 2, 2025
Copy link

🚀 Thanks for opening this pull request!

Copy link

coderabbitai bot commented May 2, 2025

📝 Walkthrough

Walkthrough

The change updates the version of the "@aws-sdk/client-s3" dependency in the package.json file from 3.779.0 to 3.787.0. No other dependencies or configurations are altered, and there are no modifications to exported or public entities within the codebase.

Changes

File Change Summary
package.json Updated "@aws-sdk/client-s3" dependency version to 3.787.0.

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

codecov bot commented May 2, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.18%. Comparing base (66c7dc6) to head (fc95ed4).
Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #261   +/-   ##
=======================================
  Coverage   97.18%   97.18%           
=======================================
  Files           2        2           
  Lines         213      213           
=======================================
  Hits          207      207           
  Misses          6        6           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@parseplatformorg
Copy link
Contributor Author

🎉 Snyk checks have passed. No issues have been found so far.

security/snyk check is complete. No issues have been found. (View Details)

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 66c7dc6 and fc95ed4.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (1)
  • package.json (1 hunks)

Comment on lines +22 to 23
"@aws-sdk/client-s3": "3.787.0",
"@aws-sdk/s3-request-presigner": "3.758.0"
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

❓ Verification inconclusive

Ensure version alignment between S3 client and presigner.

The @aws-sdk/s3-request-presigner remains at 3.758.0 while @aws-sdk/client-s3 was bumped to 3.787.0, which could introduce compatibility issues. Align both packages to the same version:

@@ -22,2 +22,2
-    "@aws-sdk/client-s3": "3.787.0",
-    "@aws-sdk/s3-request-presigner": "3.758.0"
+    "@aws-sdk/client-s3": "3.787.0",
+    "@aws-sdk/s3-request-presigner": "3.787.0"

Also regenerate your lockfile (package-lock.json or yarn.lock) and run the full test suite to catch any regressions.


Align @aws-sdk/s3-request-presigner version with @aws-sdk/client-s3

Ensure both AWS SDK packages use the same version to avoid compatibility issues.

• File: package.json (lines 22–23)

 "@aws-sdk/client-s3": "3.787.0",
-"@aws-sdk/s3-request-presigner": "3.758.0"
+"@aws-sdk/s3-request-presigner": "3.787.0"

After updating, regenerate your lockfile (package-lock.json or yarn.lock) and run the full test suite to catch any regressions.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
"@aws-sdk/client-s3": "3.787.0",
"@aws-sdk/s3-request-presigner": "3.758.0"
"@aws-sdk/client-s3": "3.787.0",
"@aws-sdk/s3-request-presigner": "3.787.0"
🤖 Prompt for AI Agents (early access)
In package.json at lines 22 to 23, the versions of @aws-sdk/client-s3 and @aws-sdk/s3-request-presigner are mismatched, which can cause compatibility issues. Update the version of @aws-sdk/s3-request-presigner to match the @aws-sdk/client-s3 version 3.787.0. After updating, regenerate your lockfile (package-lock.json or yarn.lock) and run the full test suite to ensure no regressions occur.

@mtrezza mtrezza closed this May 2, 2025
@mtrezza mtrezza deleted the snyk-upgrade-2489656ef9d793008ac34cf6e1957fab branch May 2, 2025 12:28
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.

3 participants