chore(deps): update dependency awscli to v1.37.0

[uniget-bot]

This PR contains the following updates:

Package	Update	Change
awscli (source, changelog)	minor	1.36.40 -> 1.37.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

aws/aws-cli (awscli)

v1.37.0

Compare Source

======

• api-change:apigateway: Documentation updates for Amazon API Gateway
• api-change:bedrock-agent-runtime: Now supports streaming for inline agents.
• api-change:cognito-identity: corrects the dual-stack endpoint configuration
• api-change:partnercentral-selling: Add Tagging support for ResourceSnapshotJob resources
• api-change:s3: This change enhances integrity protections for new SDK requests to S3. S3 SDKs now support the CRC64NVME checksum algorithm, full object checksums for multipart S3 objects, and new default integrity protections for S3 requests.
• api-change:security-ir: Increase minimum length of Threat Actor IP 'userAgent' to 1.
• api-change:sesv2: This release introduces a new recommendation in Virtual Deliverability Manager Advisor, which detects elevated complaint rates for customer sending identities.
• api-change:workspaces: Added GeneralPurpose.4xlarge & GeneralPurpose.8xlarge ComputeTypes.
• api-change:workspaces-thin-client: Mark type in MaintenanceWindow as required.
• feature:s3: The S3 client attempts to validate response checksums for all S3 API operations that support checksums. However, if the SDK has not implemented the specified checksum algorithm then this validation is skipped. Checksum validation behavior can be configured using the when_supported and when_required options - in code using the response_checksum_validation parameter for botocore.config.Config, in the shared AWS config file using response_checksum_validation, or as an env variable using AWS_RESPONSE_CHECKSUM_VALIDATION.
• feature:s3: Added support for the CRC64NVME checksum algorithm in the S3 client through the optional AWS CRT (awscrt) dependency.
• feature:s3: S3 client behavior is updated to always calculate a CRC32 checksum by default for operations that support it (such as PutObject or UploadPart), or require it (such as DeleteObjects). Checksum behavior can be configured using when_supported and when_required options - in code using the request_checksum_calculation parameter for botocore.config.Config, in the shared AWS config file using request_checksum_calculation, or as an env variable using AWS_REQUEST_CHECKSUM_CALCULATION. Note: Botocore will no longer automatically compute and populate the Content-MD5 header.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

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

---

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

---

This PR has been generated by Renovate Bot.

[nicholasdille-bot]

Auto-approved because label type/renovate is present.

[github-actions]

🔍 Vulnerabilities of ghcr.io/uniget-org/tools/aws:1.37.0

📦 Image Reference ghcr.io/uniget-org/tools/aws:1.37.0

digest	sha256:0f258510b99e1a9949e2f6c87a8a98ddb31b416636932e3179e590581f20f8d1
vulnerabilities
platform	linux/amd64
size	19 MB
packages	0

[github-actions]

Attempting automerge. See https://github.com/uniget-org/tools/actions/runs/12800561058.

[github-actions]

PR is clean and can be merged. See https://github.com/uniget-org/tools/actions/runs/12800561058.