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 boto3 from 1.35.9 to 1.35.10 #10841

Merged
merged 1 commit into from
Sep 3, 2024
Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 2, 2024

Bumps boto3 from 1.35.9 to 1.35.10.

Commits
  • 85cba10 Merge branch 'release-1.35.10'
  • 7264985 Bumping version to 1.35.10
  • 4e8bc10 Add changelog entries from botocore
  • 25ebb36 Merge branch 'release-1.35.9' into develop
  • See full diff in compare view

Most Recent Ignore Conditions Applied to This Pull Request
Dependency Name Ignore Conditions
boto3 [< 1.25, > 1.24.55]

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @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)

Bumps [boto3](https://github.com/boto/boto3) from 1.35.9 to 1.35.10.
- [Release notes](https://github.com/boto/boto3/releases)
- [Commits](boto/boto3@1.35.9...1.35.10)

---
updated-dependencies:
- dependency-name: boto3
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file python Pull requests that update Python code labels Sep 2, 2024
Copy link

dryrunsecurity bot commented Sep 2, 2024

DryRun Security Summary

The provided code change updates the requirements.txt file of the DefectDojo application to use the latest version of the boto3 library, which is required for the Celery Broker AWS (SQS) support used by the application.

Expand for full summary

Summary:

The provided code change is an update to the requirements.txt file, which is a file used to manage the dependencies of a Python-based application, in this case, the DefectDojo application. The key change is the update of the boto3 library version from 1.35.9 to 1.35.10. This library is required for the Celery Broker AWS (SQS) support, which is a messaging queue system used by the application.

From an application security perspective, this change is not particularly interesting, as updating dependencies to their latest versions is a common practice to ensure that the application is using the most secure and up-to-date versions of the libraries it relies on. However, it's always a good idea to review the changelog or release notes of the updated dependency to ensure that there are no known security vulnerabilities or breaking changes that could impact the application. Additionally, it's worth noting that the requirements.txt file lists a large number of dependencies, which can increase the attack surface of the application. It's important to ensure that all of these dependencies are properly maintained, secured, and kept up-to-date to mitigate potential security risks.

Files Changed:

  • requirements.txt: This file has been updated to include the latest version of the boto3 library, which is required for the Celery Broker AWS (SQS) support used by the DefectDojo application.

Code Analysis

We ran 9 analyzers against 1 file and 1 analyzer had findings. 8 analyzers had no findings.

Analyzer Findings
Sensitive Files Analyzer 1 finding

Riskiness

🟢 Risk threshold not exceeded.

View PR in the DryRun Dashboard.

Copy link
Contributor

@mtesauro mtesauro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved

@mtesauro mtesauro merged commit 7b5079e into dev Sep 3, 2024
73 checks passed
@dependabot dependabot bot deleted the dependabot/pip/dev/boto3-1.35.10 branch September 3, 2024 22:52
arivra pushed a commit to arivra/django-DefectDojo that referenced this pull request Sep 6, 2024
Bumps [boto3](https://github.com/boto/boto3) from 1.35.9 to 1.35.10.
- [Release notes](https://github.com/boto/boto3/releases)
- [Commits](boto/boto3@1.35.9...1.35.10)

---
updated-dependencies:
- dependency-name: boto3
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
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 python Pull requests that update Python code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants