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

fix(deps): update dependency botocore to v1.36.6 #1751

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

Conversation

red-hat-konflux[bot]
Copy link
Contributor

@red-hat-konflux red-hat-konflux bot commented Jan 11, 2025

This PR contains the following updates:

Package Type Update Change
botocore dependencies minor 1.35.92 -> 1.36.6

Release Notes

boto/botocore (botocore)

v1.36.6

Compare Source

======

  • api-change:cloudtrail: This release introduces the SearchSampleQueries API that allows users to search for CloudTrail Lake sample queries.
  • api-change:eks: Adds support for UpdateStrategies in EKS Managed Node Groups.
  • api-change:healthlake: Added new authorization strategy value 'SMART_ON_FHIR' for CreateFHIRDatastore API to support Smart App 2.0
  • api-change:ssm: Systems Manager doc-only update for January, 2025.
  • api-change:sso-oidc: Fixed typos in the descriptions.
  • api-change:transfer: Added CustomDirectories as a new directory option for storing inbound AS2 messages, MDN files and Status files.

v1.36.5

Compare Source

======

  • api-change:ec2: Added "future" allocation type for future dated capacity reservation

v1.36.4

Compare Source

======

  • api-change:bedrock-agent-runtime: Adds multi-turn input support for an Agent node in an Amazon Bedrock Flow
  • api-change:glue: Docs Update for timeout changes
  • api-change:medialive: AWS Elemental MediaLive adds a new feature, ID3 segment tagging, in CMAF Ingest output groups. It allows customers to insert ID3 tags into every output segment, controlled by a newly added channel schedule action Id3SegmentTagging.
  • api-change:workspaces-thin-client: Rename WorkSpaces Web to WorkSpaces Secure Browser

v1.36.3

Compare Source

======

  • api-change:batch: Documentation-only update: clarified the description of the shareDecaySeconds parameter of the FairsharePolicy data type, clarified the description of the priority parameter of the JobQueueDetail data type.
  • api-change:cognito-idp: corrects the dual-stack endpoint configuration for cognitoidp
  • api-change:connect: Added DeleteContactFlowVersion API and the CAMPAIGN flow type
  • api-change:emr-serverless: Increasing entryPoint in SparkSubmit to accept longer script paths. New limit is 4kb.
  • api-change:iotsitewise: AWS IoT SiteWise now supports ingestion and querying of Null (all data types) and NaN (double type) values of bad or uncertain data quality. New partial error handling prevents data loss during ingestion. Enabled by default for new customers; existing customers can opt-in.
  • api-change:logs: Documentation-only update to address doc errors
  • api-change:quicksight: Added DigitGroupingStyle in ThousandsSeparator to allow grouping by LAKH( Indian Grouping system ) currency. Support LAKH and CRORE currency types in Column Formatting.
  • api-change:sns: This release adds support for the topic attribute FifoThroughputScope for SNS FIFO topics. For details, see the documentation history in the Amazon Simple Notification Service Developer Guide.

v1.36.2

Compare Source

======

  • api-change:bedrock-runtime: Allow hyphens in tool name for Converse and ConverseStream APIs
  • api-change:detective: Doc only update for Detective documentation.
  • api-change:ec2: Release u7i-6tb.112xlarge, u7i-8tb.112xlarge, u7inh-32tb.480xlarge, p5e.48xlarge, p5en.48xlarge, f2.12xlarge, f2.48xlarge, trn2.48xlarge instance types.
  • api-change:notifications: Added support for Managed Notifications, integration with AWS Organization and added aggregation summaries for Aggregate Notifications
  • api-change:sagemaker: Correction of docs for "Added support for ml.trn1.32xlarge instance type in Reserved Capacity Offering"

v1.36.1

Compare Source

======

  • api-change:ecs: The release addresses Amazon ECS documentation tickets.
  • api-change:sagemaker: Added support for ml.trn1.32xlarge instance type in Reserved Capacity Offering

v1.36.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.
  • enhancement:AWSCRT: Update awscrt version to 0.23.4
  • 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.

v1.35.99

Compare Source

=======

  • api-change:gamelift: Amazon GameLift releases a new game session placement feature: PriorityConfigurationOverride. You can now override how a game session queue prioritizes placement locations for a single StartGameSessionPlacement request.
  • api-change:route53: Amazon Route 53 now supports the Mexico (Central) Region (mx-central-1) for latency records, geoproximity records, and private DNS for Amazon VPCs in that region

v1.35.98

Compare Source

=======

  • api-change:artifact: Support resolving regional API calls to partition's leader region endpoint.
  • api-change:bedrock: With this release, Bedrock Evaluation will now support latency-optimized inference for foundation models.
  • api-change:ec2: Add support for DisconnectOnSessionTimeout flag in CreateClientVpnEndpoint and ModifyClientVpnEndpoint requests and DescribeClientVpnEndpoints responses
  • api-change:kafkaconnect: Support updating connector configuration via UpdateConnector API. Release Operations API to monitor the status of the connector operation.
  • api-change:transcribe: This update provides tagging support for Transcribe's Call Analytics Jobs and Call Analytics Categories.

v1.35.97

Compare Source

=======

  • api-change:redshift: Additions to the PubliclyAccessible and Encrypted parameters clarifying what the defaults are.
  • api-change:securitylake: Doc only update for ServiceName that fixes several customer-reported issues
  • api-change:sts: Fixed typos in the descriptions.

v1.35.96

Compare Source

=======

  • api-change:codebuild: AWS CodeBuild Now Supports BuildBatch in Reserved Capacity and Lambda
  • api-change:compute-optimizer: This release expands AWS Compute Optimizer rightsizing recommendation support for Amazon EC2 Auto Scaling groups to include those with scaling policies and multiple instance types.
  • api-change:fms: AWS Firewall Manager now lets you combine multiple resource tags using the logical AND operator or the logical OR operator.

v1.35.95

Compare Source

=======

  • api-change:rds: Updates Amazon RDS documentation to clarify the RestoreDBClusterToPointInTime description.
  • api-change:route53: Amazon Route 53 now supports the Asia Pacific (Thailand) Region (ap-southeast-7) for latency records, geoproximity records, and private DNS for Amazon VPCs in that region
  • api-change:sagemaker: Adds support for IPv6 for SageMaker HyperPod cluster nodes.

v1.35.94

Compare Source

=======

  • api-change:cloudhsmv2: Adds support to ModifyCluster for modifying a Cluster's Hsm Type.
  • api-change:dynamodb: This release makes Amazon DynamoDB point-in-time-recovery (PITR) to be configurable. You can set PITR recovery period for each table individually to between 1 and 35 days.
  • api-change:imagebuilder: This release adds support for importing images from ISO disk files. Added new ImportDiskImage API operation.

v1.35.93

Compare Source

=======

  • api-change:iotsecuretunneling: Adds dualstack endpoint support for IoT Secure Tunneling
  • api-change:supplychain: Allow vanity DNS domain when creating a new ASC instance

Configuration

📅 Schedule: Branch creation - "after 5am on saturday" in timezone Europe/Prague, 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

To execute skipped test pipelines write comment /ok-to-test.

This PR has been generated by MintMaker (powered by Renovate Bot).

Copy link

jira-linking bot commented Jan 11, 2025

Commits missing Jira IDs:
54bb2c5

@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 67.91%. Comparing base (0c3c1a9) to head (49e3628).
Report is 29 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1751      +/-   ##
==========================================
+ Coverage   67.88%   67.91%   +0.03%     
==========================================
  Files          54       54              
  Lines        6041     6072      +31     
==========================================
+ Hits         4101     4124      +23     
- Misses       1940     1948       +8     

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

@red-hat-konflux red-hat-konflux bot changed the title fix(deps): update dependency botocore to v1.35.97 fix(deps): update dependency botocore to v1.36.2 Jan 18, 2025
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/mintmaker/master/botocore-1.x-lockfile branch 2 times, most recently from 07d1c6d to 5254ebb Compare January 18, 2025 12:11
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/mintmaker/master/botocore-1.x-lockfile branch from 5254ebb to 5c0da0b Compare January 25, 2025 04:20
@red-hat-konflux red-hat-konflux bot changed the title fix(deps): update dependency botocore to v1.36.2 fix(deps): update dependency botocore to v1.36.6 Jan 25, 2025
Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/mintmaker/master/botocore-1.x-lockfile branch from 5c0da0b to 54bb2c5 Compare January 25, 2025 12: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.

1 participant