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 io.swagger.core.v3:swagger-models from 2.1.13 to 2.2.1 #465

Closed
wants to merge 1 commit into from

Conversation

Artur-
Copy link
Member

@Artur- Artur- commented Jul 8, 2022

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade io.swagger.core.v3:swagger-models from 2.1.13 to 2.2.1.

ℹ️ 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 2 versions ahead of your current version.
  • The recommended version was released 22 days ago, on 2022-06-15.

The recommended version fixes:

Severity Issue PriorityScore (*) Exploit Maturity
Denial of Service (DoS)
SNYK-JAVA-COMFASTERXMLJACKSONCORE-2421244
589/1000
Why? Has a fix available, CVSS 7.5
No Known Exploit
Denial of Service (DoS)
SNYK-JAVA-COMFASTERXMLJACKSONCORE-2326698
589/1000
Why? Has a fix available, CVSS 7.5
No Known Exploit

(*) 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:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@sonarcloud
Copy link

sonarcloud bot commented Jul 8, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@codecov
Copy link

codecov bot commented Jul 8, 2022

Codecov Report

Merging #465 (a1229bf) into main (a605837) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #465   +/-   ##
=======================================
  Coverage   96.41%   96.41%           
=======================================
  Files          27       27           
  Lines        4354     4354           
  Branches      277      277           
=======================================
  Hits         4198     4198           
  Misses        152      152           
  Partials        4        4           
Flag Coverage Δ
unittests 96.41% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.


Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a605837...a1229bf. Read the comment docs.

Comment on lines +54 to 56
<swagger.version>2.2.1</swagger.version>
<swagger.codegen.version>3.0.34</swagger.codegen.version>
<swagger.codegen.generators.version>1.0.34</swagger.codegen.generators.version>
Copy link
Contributor

Choose a reason for hiding this comment

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

This patch breaks the application as some method is missing. I guess we have to bump all Swagger-related versions to make it work.

@cromoteca
Copy link
Contributor

Cannot use latest swagger due to #462

@cromoteca cromoteca closed this Aug 11, 2022
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.

None yet

3 participants