Bump boto3 from 1.19.4 to 1.19.5
Created by: dependabot[bot]
Bumps boto3 from 1.19.4 to 1.19.5.
Changelog
Sourced from boto3's changelog.
1.19.5
- api-change:
autoscaling
: [botocore
] This release adds support for attribute-based instance type selection, a new EC2 Auto Scaling feature that lets customers express their instance requirements as a set of attributes, such as vCPU, memory, and storage.- api-change:
ec2
: [botocore
] This release adds: attribute-based instance type selection for EC2 Fleet, Spot Fleet, a feature that lets customers express instance requirements as attributes like vCPU, memory, and storage; and Spot placement score, a feature that helps customers identify an optimal location to run Spot workloads.- enhancement:Session: Added
get_partition_for_region
to lookup partition for a given region_name- api-change:
eks
: [botocore
] EKS managed node groups now support BOTTLEROCKET_x86_64 and BOTTLEROCKET_ARM_64 AMI types.- api-change:
sagemaker
: [botocore
] This release allows customers to describe one or more versioned model packages through BatchDescribeModelPackage, update project via UpdateProject, modify and read customer metadata properties using Create, Update and Describe ModelPackage and enables cross account registration of model packages.- enhancement:Session: [
botocore
] Addedget_partition_for_region
allowing partition lookup by region name.- api-change:
textract
: [botocore
] This release adds support for asynchronously analyzing invoice and receipt documents through two new APIs: StartExpenseAnalysis and GetExpenseAnalysis- enchancement:
s3
: TransferConfig now supports themax_bandwidth
argument.
Commits
-
527297d
Merge branch 'release-1.19.5' -
6967a2d
Bumping version to 1.19.5 -
5d20ca0
Add changelog entries from botocore -
371f6d3
Add get_partition_for_region to Session (#3060) -
c5487b5
Add max_bandwidth to TransferConfig (#3059) -
ce77775
Merge branch 'release-1.19.4' into develop - See full diff in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebase
will rebase this PR -
@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it -
@dependabot merge
will merge this PR after your CI passes on it -
@dependabot squash and merge
will squash and merge this PR after your CI passes on it -
@dependabot cancel merge
will cancel a previously requested merge and block automerging -
@dependabot reopen
will reopen this PR if it is closed -
@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)