Skip to content

refactor: Upgrade @aws-sdk/s3-request-presigner from 3.787.0 to 3.815.0 #284

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 Jun 12, 2025

snyk-top-banner

Snyk has created this PR to upgrade @aws-sdk/s3-request-presigner from 3.787.0 to 3.815.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 13 versions ahead of your current version.

  • The recommended version was released 22 days ago.

Release notes
Package name: @aws-sdk/s3-request-presigner
  • 3.815.0 - 2025-05-21

    3.815.0(2025-05-21)

    Documentation Changes
    • client-application-auto-scaling: Doc only update that addresses a customer reported issue. (1076a5e6)
    New Features
    • clients: update client endpoints as of 2025-05-21 (153ceba3)
    • client-bedrock-agent-runtime: Amazon Bedrock introduces asynchronous flows (in preview), which let you run flows for longer durations and yield control so that your application can perform other tasks and you don't have to actively monitor the flow's progress. (9128be8e)
    • client-cloudwatch: Adds support for setting up Contributor Insight rules on logs transformed via Logs Transformation feature. (0eed8726)
    • client-ec2: Release of Dualstack and Ipv6-only EC2 Public DNS hostnames (b9f691a5)
    • client-partnercentral-selling: Modified validation to allow expectedCustomerSpend array with zero elements in Partner Opportunity operations. (ed51782d)
    Tests
    • middleware-flexible-checksums: increase hook timeout to 60s for middleware-md5-fallback.e2e (#7095) (c57206a4)

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

  • 3.812.0 - 2025-05-16

    3.812.0(2025-05-16)

    Documentation Changes
    • client-ecs: This is an Amazon ECs documentation only release to support the change of the container exit "reason" field from 255 characters to 1024 characters. (88cb2cfc)
    New Features
    • clients: update client endpoints as of 2025-05-16 (9a8d9b5d)
    • client-bedrock-data-automation: Add support for VIDEO modality to BlueprintType enum. (5657cb1e)
    • client-codepipeline: CodePipeline now supports new API ListDeployActionExecutionTargets that lists the deployment target details for deploy action executions. (eb51d8f6)
    • client-emr: Added APIs for managing Application UIs: Access Persistent (serverless) UIs via CreatePersistentAppUI DescribePersistentAppUI & GetPersistentAppUIPresignedURL, and Cluster-based UIs through GetOnClusterAppUIPresignedURL. Supports Yarn, Spark History, and TEZ interfaces. (f1f82e19)
    • client-neptune: This release adds Global Cluster Switchover capability which enables you to change your global cluster's primary AWS Region, the region that serves writes, while preserving the replication between all regions in the global cluster. (ab547b08)
    • client-glue: Changes include (1) Excel as S3 Source type and XML and Tableau's Hyper as S3 Sink types, (2) targeted number of partitions parameter in S3 sinks and (3) new compression types in CSV/JSON and Parquet S3 sinks. (a5f2aef9)
    • client-service-quotas: This release introduces CreateSupportCase operation to SDK. (611d06e0)
    • client-bedrock-data-automation-runtime: Add AssetProcessingConfiguration for video segment to InputConfiguration (bbf9999d)
    Bug Fixes
    • core/protocols: read error code case-insensitively (#7085) (c13a2a07)
    Tests

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

  • 3.810.0 - 2025-05-14

    3.810.0(2025-05-14)

    Chores
    New Features
    • client-cloudwatch-logs: This release adds a new API "ListLogGroups" and an improvement in API "DescribeLogGroups" (9d801db0)
    • client-cognito-identity-provider: Add exceptions to WebAuthn operations. (d56b4892)
    • client-mediaconvert: This update enables cropping for video overlays and adds a new STL to Teletext upconversion toggle to preserve styling. (e87d8b48)
    • client-firehose: This release adds catalogARN support for s3 tables multi-catalog catalogARNs. (7f8490a8)

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

  • 3.808.0 - 2025-05-12

    3.808.0(2025-05-12)

    Chores
    • core: return httpBearerAuth in authSchemePreference if token is set in env (#7067) (320bc3a2)
    • clients: update smithy versions to get loader config types (#7072) (d6920e8c)
    New Features
    • clients: update client endpoints as of 2025-05-12 (a476498d)
    • client-ec2: EC2 - Adding support for AvailabilityZoneId (c7ea9041)
    • client-mediatailor: Documenting that EnabledLoggingStrategies is always present in responses of PlaybackConfiguration read operations. (bf0301e7)
    • client-iam: Updating the endpoint list for the Identity and access management (IAM) service (854b130d)
    • client-medialive: Add support to the AV1 rate control mode (f8e9f567)
    • client-deadline: AWS Deadline Cloud service-managed fleets now support configuration scripts. Configuration scripts make it easy to install additional software, like plugins and packages, onto a worker. (11819667)
    • client-s3-control: Updates to support S3 Express zonal endpoints for directory buckets in AWS CLI (db31822a)
    • client-sagemaker: No API changes from previous release. This release migrated the model to Smithy keeping all features unchanged. (e06ca015)
    • client-supplychain: Launch new AWS Supply Chain public APIs for DataIntegrationEvent, DataIntegrationFlowExecution and DatasetNamespace. Also add more capabilities to existing public APIs to support direct dataset event publish, data deduplication in DataIntegrationFlow, partition specification of custom datasets. (d647fdf4)

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

  • 3.806.0 - 2025-05-08

    3.806.0(2025-05-08)

    Chores
    • deps: pass signing name to env credential provider (#7064) (801cece8)
    • clients: populate logger in loaderConfig (#7061) (48bdda33)
    Documentation Changes
    • client-guardduty: Updated description of a data structure. (c9ce9447)
    • client-cloudfront: Doc-only update for CloudFront. These changes include customer-reported issues. (5a23f2f5)
    New Features
    • clients: update client endpoints as of 2025-05-08 (ece09fe8)
    • client-sso-admin: Update PutPermissionBoundaryToPermissionSet API's managedPolicyArn pattern to allow valid ARN only. Update ApplicationName to allow white spaces. (bc0de81a)
    • client-ec2: Launching the feature to support ENA queues offering flexibility to support multiple queues per Enhanced Network Interface (ENI) (b9b5b6ce)
    • client-glue: This new release supports customizable RefreshInterval for all Saas ZETL integrations from 15 minutes to 6 days. (d6e00491)
    • client-codepipeline: Add support for Secrets Manager and Plaintext environment variable types in Commands action (753bf4e0)
    Bug Fixes
    • codegen: allow overwriting protocol priority order (#7066) (dc4edaa0)
    Tests
    • client-s3: integration for config 'authSchemePreference' (#7063) (49c6f99d)

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

  • 3.804.0 - 2025-05-06
  • 3.803.0 - 2025-05-05
  • 3.802.0 - 2025-05-02
  • 3.800.0 - 2025-04-30
  • 3.799.0 - 2025-04-29
  • 3.798.0 - 2025-04-28
  • 3.797.0 - 2025-04-25
  • 3.796.0 - 2025-04-24
  • 3.787.0 - 2025-04-10
from @aws-sdk/s3-request-presigner 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 version of a backend dependency to ensure compatibility and access to the latest features and fixes.

Snyk has created this PR to upgrade @aws-sdk/s3-request-presigner from 3.787.0 to 3.815.0.

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

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/s3-request-presigner from 3.787.0 to 3.815.0 refactor: Upgrade @aws-sdk/s3-request-presigner from 3.787.0 to 3.815.0 Jun 12, 2025
Copy link

🚀 Thanks for opening this pull request!

Copy link

coderabbitai bot commented Jun 12, 2025

📝 Walkthrough

Walkthrough

The dependency "@aws-sdk/s3-request-presigner" in the package.json file was updated from version 3.787.0 to 3.815.0. No other files or dependencies were modified.

Changes

File(s) Change Summary
package.json Updated "@aws-sdk/s3-request-presigner" version from 3.787.0 to 3.815.0

Possibly related PRs


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 8f7791d and b5dfda2.

⛔ 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)
🚧 Files skipped from review as they are similar to previous changes (1)
  • package.json
⏰ Context from checks skipped due to timeout of 90000ms (6)
  • GitHub Check: Parse Server 8, Node.js 20
  • GitHub Check: Parse Server 8, Node.js 22
  • GitHub Check: Parse Server 8, Node.js 18
  • GitHub Check: Parse Server 7, Node.js 20
  • GitHub Check: Parse Server 7, Node.js 22
  • GitHub Check: Parse Server 7, Node.js 18

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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 auto-generate unit tests to generate unit tests for 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.

@parseplatformorg
Copy link
Contributor Author

parseplatformorg commented Jun 12, 2025

🎉 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

codecov bot commented Jun 12, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.19%. Comparing base (6eae9e1) to head (b5dfda2).
Report is 3 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #284   +/-   ##
=======================================
  Coverage   97.19%   97.19%           
=======================================
  Files           2        2           
  Lines         214      214           
=======================================
  Hits          208      208           
  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.

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

🧹 Nitpick comments (1)
package.json (1)

23-23: Ensure AWS SDK version compatibility across packages.

The @aws-sdk/client-s3 dependency is pinned at 3.824.0 while @aws-sdk/s3-request-presigner is updated to 3.815.0. Mixing minor versions can introduce subtle API mismatches—consider aligning both to the same minor version (e.g., 3.824.0) or verifying compatibility between these releases.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 15ab6a0 and 8f7791d.

⛔ 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)
⏰ Context from checks skipped due to timeout of 90000ms (6)
  • GitHub Check: Parse Server 7, Node.js 20
  • GitHub Check: Parse Server 8, Node.js 20
  • GitHub Check: Parse Server 8, Node.js 18
  • GitHub Check: Parse Server 7, Node.js 22
  • GitHub Check: Parse Server 8, Node.js 22
  • GitHub Check: Parse Server 7, Node.js 18

@@ -20,7 +20,7 @@
"homepage": "https://github.com/parse-community/parse-server-s3-adapter#readme",
"dependencies": {
"@aws-sdk/client-s3": "3.824.0",
"@aws-sdk/s3-request-presigner": "3.787.0"
"@aws-sdk/s3-request-presigner": "3.815.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

🧩 Analysis chain

Validate the security update and run dependency audit.

After bumping the presigner package, reinstall dependencies and run an audit to confirm the Snyk-reported vulnerability is resolved and no new issues have been introduced.


🏁 Script executed:

#!/bin/bash
npm ci
npm audit

Length of output: 9815


Remaining vulnerabilities detected after audit

The npm audit report shows 15 unresolved issues (including 2 critical and 4 high) related to transitive dependencies of @aws-sdk/s3-request-presigner bump:

• Critical:
– crypto-js (PBKDF2 weakness)
• High:
– cross-spawn (ReDoS)
– path-to-regexp (ReDoS)
– ws (DoS via headers)
– others

Action items:

  • Run npm audit fix to address non-breaking issues.
  • For fixes marked “--force” (breaking changes), evaluate upgrading/removing the following top-level dependencies:
    • parse & parse-server (crypto-js, ws, tough-cookie)
    • express (path-to-regexp)
    • @babel/runtime & helpers (named group RegExp issue)
  • After upgrades, rerun npm ci && npm audit to confirm zero vulnerabilities.

Please prioritize resolving or safely mitigating the remaining findings before merging.

🤖 Prompt for AI Agents
In package.json at line 23, after updating the @aws-sdk/s3-request-presigner
dependency, run npm ci and npm audit to identify remaining vulnerabilities. Then
run npm audit fix to automatically resolve non-breaking issues. For
vulnerabilities requiring breaking changes, evaluate upgrading or removing
top-level dependencies such as parse, parse-server, express, and @babel/runtime
as indicated. After making these changes, reinstall dependencies and rerun npm
audit to ensure all vulnerabilities are resolved before merging.

@mtrezza mtrezza closed this Jun 14, 2025
@mtrezza mtrezza deleted the snyk-upgrade-b755cab69bb0e56a63305eaa4b2f9787 branch June 14, 2025 16:21
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