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

[Snyk] Upgrade org.springframework:spring-web from 6.1.6 to 6.1.13 #82

Closed

Conversation

shafeeqd959
Copy link

snyk-top-banner

Snyk has created this PR to upgrade org.springframework:spring-web from 6.1.6 to 6.1.13.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 7 versions ahead of your current version.

  • The recommended version was released on a month ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
medium severity Denial of Service (DoS)
SNYK-JAVA-ORGSPRINGFRAMEWORK-7687447
559 No Known Exploit

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Snyk has created this PR to upgrade org.springframework:spring-web from 6.1.6 to 6.1.13.

See this package in maven:
org.springframework:spring-web

See this project in Snyk:
https://app.snyk.io/org/contentstack-devex/project/ca5ef3ed-c635-49d7-8224-9709959d8bd8?utm_source=github&utm_medium=referral&page=upgrade-pr
@shafeeqd959 shafeeqd959 requested a review from a team as a code owner October 18, 2024 01:20
Copy link

We regret to inform you that you are currently not able to merge your changes into the master branch due to restrictions applied by our SRE team. To proceed with merging your changes, we kindly request that you create a pull request from the next branch. Our team will then review the changes and work with you to ensure a successful merge into the master branch.

@reeshika-h reeshika-h force-pushed the snyk-upgrade-b649b70a6e94029277a8538f7b2d3119 branch from abb848d to 76bfada Compare October 18, 2024 06:04
Copy link

We regret to inform you that you are currently not able to merge your changes into the master branch due to restrictions applied by our SRE team. To proceed with merging your changes, we kindly request that you create a pull request from the next branch. Our team will then review the changes and work with you to ensure a successful merge into the master branch.

@reeshika-h reeshika-h force-pushed the snyk-upgrade-b649b70a6e94029277a8538f7b2d3119 branch from 76bfada to 77bedc1 Compare October 18, 2024 06:16
Copy link

We regret to inform you that you are currently not able to merge your changes into the master branch due to restrictions applied by our SRE team. To proceed with merging your changes, we kindly request that you create a pull request from the next branch. Our team will then review the changes and work with you to ensure a successful merge into the master branch.

@reeshika-h reeshika-h force-pushed the snyk-upgrade-b649b70a6e94029277a8538f7b2d3119 branch from 77bedc1 to d68f1c5 Compare October 18, 2024 06:25
Copy link

We regret to inform you that you are currently not able to merge your changes into the master branch due to restrictions applied by our SRE team. To proceed with merging your changes, we kindly request that you create a pull request from the next branch. Our team will then review the changes and work with you to ensure a successful merge into the master branch.

1 similar comment
Copy link

We regret to inform you that you are currently not able to merge your changes into the master branch due to restrictions applied by our SRE team. To proceed with merging your changes, we kindly request that you create a pull request from the next branch. Our team will then review the changes and work with you to ensure a successful merge into the master branch.

@reeshika-h reeshika-h force-pushed the snyk-upgrade-b649b70a6e94029277a8538f7b2d3119 branch from d68f1c5 to a5a404c Compare October 18, 2024 06:32
Copy link

We regret to inform you that you are currently not able to merge your changes into the master branch due to restrictions applied by our SRE team. To proceed with merging your changes, we kindly request that you create a pull request from the next branch. Our team will then review the changes and work with you to ensure a successful merge into the master branch.

1 similar comment
Copy link

We regret to inform you that you are currently not able to merge your changes into the master branch due to restrictions applied by our SRE team. To proceed with merging your changes, we kindly request that you create a pull request from the next branch. Our team will then review the changes and work with you to ensure a successful merge into the master branch.

@reeshika-h reeshika-h force-pushed the snyk-upgrade-b649b70a6e94029277a8538f7b2d3119 branch from a5a404c to 5d39f0a Compare October 18, 2024 10:47
Copy link

We regret to inform you that you are currently not able to merge your changes into the master branch due to restrictions applied by our SRE team. To proceed with merging your changes, we kindly request that you create a pull request from the next branch. Our team will then review the changes and work with you to ensure a successful merge into the master branch.

1 similar comment
Copy link

We regret to inform you that you are currently not able to merge your changes into the master branch due to restrictions applied by our SRE team. To proceed with merging your changes, we kindly request that you create a pull request from the next branch. Our team will then review the changes and work with you to ensure a successful merge into the master branch.

@aravindbuilt aravindbuilt force-pushed the snyk-upgrade-b649b70a6e94029277a8538f7b2d3119 branch from 5d39f0a to 36657e8 Compare October 18, 2024 11:57
Copy link

We regret to inform you that you are currently not able to merge your changes into the master branch due to restrictions applied by our SRE team. To proceed with merging your changes, we kindly request that you create a pull request from the next branch. Our team will then review the changes and work with you to ensure a successful merge into the master branch.

1 similar comment
Copy link

We regret to inform you that you are currently not able to merge your changes into the master branch due to restrictions applied by our SRE team. To proceed with merging your changes, we kindly request that you create a pull request from the next branch. Our team will then review the changes and work with you to ensure a successful merge into the master branch.

@reeshika-h
Copy link
Contributor

Fixes done in PR #83

@reeshika-h reeshika-h closed this Oct 18, 2024
@reeshika-h reeshika-h deleted the snyk-upgrade-b649b70a6e94029277a8538f7b2d3119 branch October 18, 2024 12:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants