renovate-bot opened a new pull request, #1093:
URL: https://github.com/apache/polaris/pull/1093

   This PR contains the following updates:
   
   | Package | Change | Age | Adoption | Passing | Confidence |
   |---|---|---|---|---|---|
   | [boto3](https://redirect.github.com/boto/boto3) | `==1.37.0` -> `==1.37.4` 
| 
[![age](https://developer.mend.io/api/mc/badges/age/pypi/boto3/1.37.4?slim=true)](https://docs.renovatebot.com/merge-confidence/)
 | 
[![adoption](https://developer.mend.io/api/mc/badges/adoption/pypi/boto3/1.37.4?slim=true)](https://docs.renovatebot.com/merge-confidence/)
 | 
[![passing](https://developer.mend.io/api/mc/badges/compatibility/pypi/boto3/1.37.0/1.37.4?slim=true)](https://docs.renovatebot.com/merge-confidence/)
 | 
[![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/boto3/1.37.0/1.37.4?slim=true)](https://docs.renovatebot.com/merge-confidence/)
 |
   
   ---
   
   ### Release Notes
   
   <details>
   <summary>boto/boto3 (boto3)</summary>
   
   ### 
[`v1.37.4`](https://redirect.github.com/boto/boto3/blob/HEAD/CHANGELOG.rst#1374)
   
   [Compare 
Source](https://redirect.github.com/boto/boto3/compare/1.37.3...1.37.4)
   
   \======
   
   -   api-change:`bedrock-agent`: \[`botocore`] This release lets Amazon 
Bedrock Flows support newer models by increasing the maximum length of output 
in a prompt configuration. This release also increases the maximum number of 
prompt variables to 20 and the maximum number of node inputs to 20.
   -   api-change:`bedrock-data-automation`: \[`botocore`] Renamed and added 
new StandardConfiguration enums. Added support to update 
EncryptionConfiguration in UpdateBlueprint and UpdateDataAutomation APIs. 
Changed HttpStatus code for DeleteBlueprint and DeleteDataAutomationProject 
APIs to 200 from 204. Added APIs to support tagging.
   -   api-change:`bedrock-data-automation-runtime`: \[`botocore`] Added a 
mandatory parameter DataAutomationProfileArn to support for cross region 
inference for InvokeDataAutomationAsync API. Renamed DataAutomationArn to 
DataAutomationProjectArn. Added APIs to support tagging.
   -   api-change:`dms`: \[`botocore`] Add skipped status to the Result 
Statistics of an Assessment Run
   -   api-change:`eks`: \[`botocore`] Adding licenses to EKS Anywhere 
Subscription operations response.
   -   api-change:`mediaconvert`: \[`botocore`] The AWS MediaConvert Probe API 
allows you to analyze media files and retrieve detailed metadata about their 
content, format, and structure.
   -   api-change:`pricing`: \[`botocore`] Update GetProducts and 
DescribeServices API request input validations.
   -   api-change:`ssm`: \[`botocore`] Systems Manager doc-only updates for 
Feb. 2025.
   -   enhancement:useragent: \[`botocore`] Update user agent string to include 
client feature use.
   
   ### 
[`v1.37.3`](https://redirect.github.com/boto/boto3/blob/HEAD/CHANGELOG.rst#1373)
   
   [Compare 
Source](https://redirect.github.com/boto/boto3/compare/1.37.2...1.37.3)
   
   \======
   
   -   api-change:`bedrock-agent-runtime`: \[`botocore`] Introduces Sessions 
(preview) to enable stateful conversations in GenAI applications.
   -   api-change:`emr`: \[`botocore`] Definition update for EbsConfiguration.
   -   api-change:`qbusiness`: \[`botocore`] This release supports deleting 
attachments from conversations.
   -   api-change:`redshift-serverless`: \[`botocore`] Add track support for 
Redshift Serverless workgroup.
   -   api-change:`sagemaker`: \[`botocore`] SageMaker HubService is 
introducing support for creating Training Jobs in Curated Hub (Private Hub). 
Additionally, it is introducing two new APIs: UpdateHubContent and 
UpdateHubContentReference.
   -   api-change:`storagegateway`: \[`botocore`] This release adds support to 
invoke a process that cleans the specified file share's cache of file entries 
that are failing upload to Amazon S3.
   
   ### 
[`v1.37.2`](https://redirect.github.com/boto/boto3/blob/HEAD/CHANGELOG.rst#1372)
   
   [Compare 
Source](https://redirect.github.com/boto/boto3/compare/1.37.1...1.37.2)
   
   \======
   
   -   api-change:`application-signals`: \[`botocore`] This release adds API 
support for reading Service Level Objectives and Services from monitoring 
accounts, from SLO and Service-scoped operations, including ListServices and 
ListServiceLevelObjectives.
   -   api-change:`batch`: \[`botocore`] AWS Batch: Resource Aware Scheduling 
feature support
   -   api-change:`chime`: \[`botocore`] Removes the Amazon Chime SDK APIs from 
the "chime" namespace.  Amazon Chime SDK APIs continue to be available in the 
AWS SDK via the dedicated Amazon Chime SDK namespaces: chime-sdk-identity, 
chime-sdk-mediapipelines, chime-sdk-meetings, chime-sdk-messaging, and 
chime-sdk-voice.
   -   api-change:`cloudfront`: \[`botocore`] Documentation update for VPC 
origin config.
   -   api-change:`ec2`: \[`botocore`] Amazon EC2 Fleet customers can now 
override the Block Device Mapping specified in the Launch Template when 
creating a new Fleet request, saving the effort of creating and associating new 
Launch Templates to customize the Block Device Mapping.
   -   api-change:`iotfleetwise`: \[`botocore`] This release adds an optional 
listResponseScope request parameter in certain list API requests to limit the 
response to metadata only.
   -   api-change:`oam`: \[`botocore`] This release adds support for sharing 
AWS::ApplicationSignals::Service and 
AWS::ApplicationSignals::ServiceLevelObjective resources.
   -   api-change:`sagemaker`: \[`botocore`] AWS SageMaker InferenceComponents 
now support rolling update deployments for Inference Components.
   -   enhancement:`Protocol`: \[`botocore`] Adds support for the 
smithy-rpc-v2-cbor protocol.  If a service supports smithy-rpc-v2-cbor, this 
protocol will automatically be used.  For more information, see 
https://smithy.io/2.0/additional-specs/protocols/smithy-rpc-v2.html
   
   ### 
[`v1.37.1`](https://redirect.github.com/boto/boto3/blob/HEAD/CHANGELOG.rst#1371)
   
   [Compare 
Source](https://redirect.github.com/boto/boto3/compare/1.37.0...1.37.1)
   
   \======
   
   -   api-change:`codebuild`: \[`botocore`] Adding "reportArns" field in 
output of BatchGetBuildBatches API. "reportArns" is an array that contains the 
ARNs of reports created by merging reports from builds associated with the 
batch build.
   -   api-change:`devicefarm`: \[`botocore`] Add an optional configuration to 
the ScheduleRun and CreateRemoteAccessSession API to set a device level http/s 
proxy.
   -   api-change:`ec2`: \[`botocore`] Adds support for time-based EBS-backed 
AMI copy operations. Time-based copy ensures that EBS-backed AMIs are copied 
within and across Regions in a specified timeframe.
   -   api-change:`iot`: \[`botocore`] AWS IoT - AWS IoT Device Defender adds 
support for a new Device Defender Audit Check that monitors device certificate 
age and custom threshold configurations for both the new device certificate age 
check and existing device certificate expiry check.
   -   api-change:`taxsettings`: \[`botocore`] PutTaxRegistration API changes 
for Egypt, Greece, Vietnam countries
   
   </details>
   
   ---
   
   ### Configuration
   
   📅 **Schedule**: Branch creation - "* 0-3 * * 1" (UTC), 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.
   
   ---
   
    - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this 
box
   
   ---
   
   This PR was generated by [Mend Renovate](https://mend.io/renovate/). View 
the [repository job log](https://developer.mend.io/github/apache/polaris).
   
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xNzYuMiIsInVwZGF0ZWRJblZlciI6IjM5LjE3Ni4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJyZW5vdmF0ZS1wb2xhcmlzIl19-->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to