Skip to content

2.1.0 version uses swagger-parser v2.1.26 which has a known issue that causes NPE #782

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.

Sign up for GitHub

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

Jump to bottom
Closed
VictorPascualV opened this issue May 12, 2025 · 2 comments
Closed

2.1.0 version uses swagger-parser v2.1.26 which has a known issue that causes NPE #782

VictorPascualV opened this issue May 12, 2025 · 2 comments
Milestone
2.2.0

Comments

@VictorPascualV
Copy link

VictorPascualV commented May 12, 2025 •
edited
Loading

openapi-diff v2.1.0 uses swagger-parser v2.1.26, which has the following known issue: swagger-api/swagger-parser#2166

A new version of swagger-parser has been released, which fixed this known issue (v2.1.27).

Currently, we can not bump to openapi-diff-core v2.1.0 because the known issue in swagger-parser v2.1.26 is breaking the build in some of our consumer services.

Please release a new version of openapi-diff-core that uses the new swagger-parser v2.1.27.

Thanks!
@DrSatyr DrSatyr modified the milestones: 2.1.0, 2.2.0 May 12, 2025
@DrSatyr
Copy link
Collaborator

DrSatyr commented May 12, 2025

Sure, 2.1.27 is already in place. Will release 2.1.1 then.

@DrSatyr DrSatyr closed this as completed May 12, 2025
@VictorPascualV
Copy link
Author

Thanks a lot for addressing that so quickly! 🙌

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2.2.0
Development

No branches or pull requests
2 participants
@VictorPascualV @DrSatyr