Skip to content

Conversation

@dependabot-preview
Copy link
Contributor

Bumps boto3 from 1.12.21 to 1.16.63.

Changelog

Sourced from boto3's changelog.

1.16.63

  • api-change:macie2: [botocore] Update macie2 client to latest version
  • api-change:connect: [botocore] Update connect client to latest version
  • api-change:medialive: [botocore] Update medialive client to latest version

1.16.62

  • api-change:wellarchitected: [botocore] Update wellarchitected client to latest version
  • api-change:managedblockchain: [botocore] Update managedblockchain client to latest version
  • api-change:cloudwatch: [botocore] Update cloudwatch client to latest version
  • api-change:databrew: [botocore] Update databrew client to latest version
  • bugfix:Validator: [botocore] Fix showing incorrect max-value in error message for range and length value validation
  • api-change:iot: [botocore] Update iot client to latest version
  • api-change:robomaker: [botocore] Update robomaker client to latest version

1.16.61

  • api-change:elasticache: [botocore] Update elasticache client to latest version
  • api-change:customer-profiles: [botocore] Update customer-profiles client to latest version
  • api-change:sesv2: [botocore] Update sesv2 client to latest version
  • api-change:accessanalyzer: [botocore] Update accessanalyzer client to latest version
  • api-change:lightsail: [botocore] Update lightsail client to latest version
  • api-change:es: [botocore] Update es client to latest version

1.16.60

  • api-change:backup: [botocore] Update backup client to latest version

1.16.59

  • api-change:greengrassv2: [botocore] Update greengrassv2 client to latest version
  • api-change:redshift: [botocore] Update redshift client to latest version
  • api-change:lexv2-runtime: [botocore] Update lexv2-runtime client to latest version
  • api-change:rds: [botocore] Update rds client to latest version
  • api-change:lexv2-models: [botocore] Update lexv2-models client to latest version
  • api-change:ssm: [botocore] Update ssm client to latest version
  • api-change:ec2: [botocore] Update ec2 client to latest version

1.16.58

  • api-change:securityhub: [botocore] Update securityhub client to latest version
  • api-change:kafka: [botocore] Update kafka client to latest version
  • api-change:resourcegroupstaggingapi: [botocore] Update resourcegroupstaggingapi client to latest version

... (truncated)

Commits
  • d77d24f Merge branch 'release-1.16.63'
  • 346f516 Bumping version to 1.16.63
  • cb7a593 Add changelog entries from botocore
  • 3c261c0 Merge branch 'release-1.16.62'
  • 04642cf Merge branch 'release-1.16.62' into develop
  • 835f92b Bumping version to 1.16.62
  • 2cecaac Add changelog entries from botocore
  • 79e949a Merge branch 'release-1.16.61' into develop
  • cdfb0d2 Merge branch 'release-1.16.61'
  • 689ed1e Bumping version to 1.16.61
  • Additional commits viewable in compare view

Dependabot compatibility score

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)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Automerge options (never/patch/minor, and dev/runtime dependencies)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

Bumps [boto3](https://github.com/boto/boto3) from 1.12.21 to 1.16.63.
- [Release notes](https://github.com/boto/boto3/releases)
- [Changelog](https://github.com/boto/boto3/blob/develop/CHANGELOG.rst)
- [Commits](boto/boto3@1.12.21...1.16.63)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
@dependabot-preview dependabot-preview bot added the dependencies Pull requests that update a dependency file label Feb 1, 2021
@dependabot-preview
Copy link
Contributor Author

Superseded by #61.

@dependabot-preview dependabot-preview bot deleted the dependabot/pip/boto3-1.16.63 branch March 1, 2021 10:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants