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

Bump github.com/aws/aws-sdk-go from 1.31.6 to 1.34.0 #1

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

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Feb 14, 2023

Bumps github.com/aws/aws-sdk-go from 1.31.6 to 1.34.0.

Changelog

Sourced from github.com/aws/aws-sdk-go's changelog.

Release v1.34.0 (2020-08-07)

Service Client Updates

  • service/glue: Updates service API and documentation
    • AWS Glue now adds support for Network connection type enabling you to access resources inside your VPC using Glue crawlers and Glue ETL jobs.
  • service/organizations: Updates service API and documentation
    • Documentation updates for some new error reasons.
  • service/s3: Updates service documentation and examples
    • Updates Amazon S3 API reference documentation.
  • service/sms: Updates service API and documentation
    • In this release, AWS Server Migration Service (SMS) has added new features: 1. APIs to work with application and instance level validation 2. Import application catalog from AWS Application Discovery Service 3. For an application you can start on-demand replication

SDK Features

  • service/s3/s3crypto: Updates to the Amazon S3 Encryption Client - This change includes fixes for issues that were reported by Sophie Schmieg from the Google ISE team, and for issues that were discovered by AWS Cryptography.

Release v1.33.21 (2020-08-06)

Service Client Updates

  • service/ec2: Updates service API, documentation, and paginators
    • This release supports Wavelength resources, including carrier gateways, and carrier IP addresses.
  • service/lex-models: Updates service API and documentation
  • service/personalize: Updates service API and documentation
  • service/personalize-events: Updates service API and documentation
  • service/personalize-runtime: Updates service API and documentation
  • service/runtime.lex: Updates service API and documentation

Release v1.33.20 (2020-08-05)

Service Client Updates

  • service/appsync: Updates service API and documentation
  • service/fsx: Updates service documentation
  • service/resourcegroupstaggingapi: Updates service documentation
    • Documentation updates for the Resource Group Tagging API namespace.
  • service/sns: Updates service documentation
    • Documentation updates for SNS.
  • service/transcribe: Updates service API, documentation, and paginators

Release v1.33.19 (2020-08-04)

Service Client Updates

  • service/health: Updates service documentation
    • Documentation updates for health

Release v1.33.18 (2020-08-03)

... (truncated)

Commits
  • ae9b9fd Release v1.34.0 (2020-08-07)
  • 1e84382 Merge commit '12ff57a16373dda5a0c22eafdf0fa1c4c224f7c4' into release
  • b811ea8 Release v1.33.21 (2020-08-06) (#3462)
  • 12ff57a Updates to the Amazon S3 Encryption Client - This change includes fixes for i...
  • 2007a98 Release v1.33.20 (2020-08-05) (#3460)
  • 39b4438 Release v1.33.19 (2020-08-04) (#3458)
  • e14cc11 Merge pull request #3432 from diehlaws/common-files-standardization
  • 9a13de7 Release v1.33.18 (2020-08-03) (#3456)
  • 41f3140 Add reference links to readme
  • 29d57fc Implementing suggested changes
  • 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

You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [github.com/aws/aws-sdk-go](https://github.com/aws/aws-sdk-go) from 1.31.6 to 1.34.0.
- [Release notes](https://github.com/aws/aws-sdk-go/releases)
- [Changelog](https://github.com/aws/aws-sdk-go/blob/v1.34.0/CHANGELOG.md)
- [Commits](aws/aws-sdk-go@v1.31.6...v1.34.0)

---
updated-dependencies:
- dependency-name: github.com/aws/aws-sdk-go
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Feb 14, 2023
@pull-request-quantifier-deprecated

This PR has 639 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!


Quantification details

Label      : Extra Large
Size       : +492 -147
Percentile : 87.97%

Total files changed: 14

Change summary by file extension:
.mod : +1 -1
.sum : +2 -98
.go : +488 -47
.txt : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

  • Fast and predictable releases to production:
    • Optimal size changes are more likely to be reviewed faster with fewer
      iterations.
    • Similarity in low PR complexity drives similar review times.
  • Review quality is likely higher as complexity is lower:
    • Bugs are more likely to be detected.
    • Code inconsistencies are more likely to be detected.
  • Knowledge sharing is improved within the participants:
    • Small portions can be assimilated better.
  • Better engineering practices are exercised:
    • Solving big problems by dividing them in well contained, smaller problems.
    • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

  • Use the PullRequestQuantifier to quantify your PR accurately
    • Create a context profile for your repo using the context generator
    • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
    • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
    • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
  • Change your engineering behaviors
    • For PRs that fall outside of the desired spectrum, review the details and check if:
      • Your PR could be split in smaller, self-contained PRs instead
      • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

  • One line was added: +1 -0
  • One line was deleted: +0 -1
  • One line was modified: +1 -1 (git diff doesn't know about modified, it will
    interpret that line like one addition plus one deletion)
  • Change percentiles: Change characteristics (addition, deletion, modification)
    of this PR in relation to all other PRs within the repository.


Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

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 Extra Large
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants